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

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

• Desktop: ObjectID -2 and ObjectID 18 contains the entire XDT file
• SDK: ObjectID -2 and ObjectID 18 contains only "<Output>"

mtSystem

• Desktop: "definition" value contains the "Schema" element of the XDT file
• SDK: "definition" value contains "<Schema name="Termbase Definition">"

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.

Kind regards

Samuel

Hi Stefan Tudorica

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

• Desktop: ObjectID -2 and ObjectID 18 contains the entire XDT file
• SDK: ObjectID -2 and ObjectID 18 contains only "<Output>"

mtSystem

• Desktop: "definition" value contains the "Schema" element of the XDT file
• SDK: "definition" value contains "<Schema name="Termbase Definition">"

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.

Kind regards

Samuel

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);

Yes, the SDK created termbase works with image:

You should try to reinstall MT.

In .csproj should be a <COMReference Include="MultiTermIX"> section. Does it look like this?

<COMReference Include="MultiTermIX">
      <Guid>{ 76DBA48C -DA18 -4FB2 - BD45 - 32752C5BD73E }</Guid>
      <VersionMajor>17</VersionMajor>
      <VersionMinor>0</VersionMinor>
      <Lcid>0</Lcid>
      <WrapperTool>tlbimp</WrapperTool>
      <Isolated>False</Isolated>
      <EmbedInteropTypes>True</EmbedInteropTypes>
 </COMReference>

Hi Stefan Tudorica,

The COM reference was missing; and can confirm that by adding it, the problem is now solved.

Thank you very much for the help.