Trados Studio
Trados Enterprise
Trados Team
Trados GroupShare
Trados Business Manager
Passolo
MultiTerm
RWS AppStore
Connectors
Beta Groups
Managed Translation
MultiTrans
TMS
WorldServer
Language Weaver
Language Weaver Connectors
Language Weaver Edge
Tridion Docs
Tridion Sites
LiveContent S1000D
XPP
Language Developers
Tridion Docs Developers
Community Help
RWS User Experience
Internal Trados Ideas Community
Mercury
RWS Community Internal Group
RWS Training & Certification
Style Guides
RWS Campus
RWS Enterprise Technology Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Nordic Tridion Docs User Group
Tridion West Coast User Group
Trados Studio Ideas
Trados GroupShare Ideas
Trados Team Ideas
Trados Team Terminology Ideas
Trados Enterprise Ideas
Trados Business Manager Ideas
MultiTerm Ideas
Passolo Ideas
RWS Appstore Ideas
Tridion Docs Ideas
Tridion Sites Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
Managed Translation - Enterprise Ideas
TMS Ideas
WorldServer Ideas
LiveContent S1000D Ideas
Contenta S1000D
XPP Ideas
Events & Webinars
To RWS Support
Detecting language please wait for.......
Got a bit of an odd one, well two actually.
I have a Definition XDT file, that contains:
When I create a termbase via MultiTerm, the Term_UUID is (correctly) not editable, and I am able to select a file for the Image:
However, if I create a termbase via the MultiTerm SDK (using the same XDT file), the Term_UUID is available to edit and the Image filed, although defined as a "Multimedia File" is defaulted to text input.
Is there a known issue/fix for this?
Thanks
Samuel
The same symptoms also occur in MultiTerm 2022.
Hi Samuel Baldus, I'll reach out to the MultiTerm team and circle back to you when I have some feedback.
Thanks Patrick Andrew Hartnett
Hi Samuel Baldus, I need your XDT file in order to investigate the issue.
Readonly should be set using Input Models, not XDT.
Hi Stefan Tudorica
Please find XDT attached.
Regarding your last comment, using the attached file in Desktop app, the XDT read only fields are correctly processed, without using InputModel.
Using the same file in the SDK the read only fields are editable.
The multimedia field is also editable as a text field.
I look forward to your feedback.
Kind regards
BALTHASAR_FRUITS.zip
I think I have found the reason why the descriptive fields are not working as expected.
I created new termbases, one with the Desktop app and the other with the SDK API.
Comparing the two termbases in MS Access, I noticed differences in the mtCatalogObjects and mtSystem tables.
mtCatalogObjects
mtSystem
I then copied the three values from the Desktop database to the SDK database, and tested the SDK in the Desktop App; and it now behaves correctly.
Why these values are not being set correctly, I cannot answer but at least it might help solving the problem.
Update: It appears that we only need to "correct" the mtCatalogObjects['Description'] fields as a workaround.
I have tried to replicate the issue (using MT 2022 latest release) but is working - for both local and remote termbases - the image field is correct.
Definition looks the same for both termbases:
There is an additional Note field that didn't appear in your screenshot - the xdt is the same?
Can you also provide me the source code or a sample project that uses SDK and reproduce the issue?
Thanks,
Stefan
The screenshot looks the same whether created with the Desktop/SDK, but that's not the problem.
Have you actually tried to add an Image to a term in a termbase created with the SDK though?
When I try using the termbase created with the SDK, it does not open the Multimedia File dialog, it reverts back to plain Text.
You may also see the read-only Term_UUID field is also available to add, which also differs to when creating the termbase via the Desktop app.
Here is the simple code used to create the termbase via the SDK. As you can see, this is pretty much straight off the SDK shelf.
Application CreateTermbaseApplication = new Application();TermbaseRepository CreateTermbaseRepository = CreateTermbaseApplication.LocalRepository; CreateTermbaseRepository.Connect("", "");Termbases CreateTermbaseTermbases = CreateTermbaseRepository.Termbases;CreateTermbaseTermbases.New(TermbaseName,TermbaseDescription,XdtFilePath,TermbaseOutput);