Dear Studio developer community,

We have recently updated our environment to Trados Studio 2024 SR1 CU3 (18.1.3.6657). Due to the change to the Selected Fields settings for termbases in SR1, the Selected Fields settings our users make in File > Options > Language Pairs > All Language Pairs > Termbases > Selected Fields are now ignored when they work on our translation projects because the Selected Fields settings of the project always take precedence. In our case, nothing is selected in the project's Selected Fields settings, so the RWS default fields are displayed in the Term Recognition window in the Studio Editor. We were told by RWS support that this behavior is by design. Due to the above issue, in order to help our users choose the correct terminology, we would need to predefine certain Selected Fields for all users. Since the SR1 change, this would usually be set in the project template and then apply to all projects created based on this template. But we have a custom-built project creation automation which creates local Studio projects based on centrally managed project templates and dynamically connects the correct server-based MultiTerm termbase (depending on the project’s language combination) only during project creation. So we cannot preset these settings in the project templates because the templates don’t actually contain a termbase entry.

I tried to find information about specifying the Selected Fields via Studio API, but I'm not sure I found the correct place in the Studio API documentation. I can't find the setting mentioned on the Adding Termbases page. The API release notes for Studio 2024 SR1 mention the new ShowInUI property for the DescriptiveField class - is that where our developer would need to specify which fields should be displayed to the users? Or is this only related to setting up a custom terminology provider, but not related to adding an existing provider to a project, and they would instead need to use another class/property?

We would appreciate more details about the API and/or code examples that could help us predefine these termbase fields. For example, on termbase level, we would need to enable the terminology domain ("component"), and on term level things like Gender, Abbreviation etc. (see attached screenshot).

Thanks,

Sophia