Studio Developers Q&A - Recent Threads

RE: Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

Dino Azzano — Thu, 13 Aug 2026 13:29:38 GMT

Hi Robert Cornea , thank you for looking into this matter and finding the problem. Upon release of Studio 2024 CU 5 Beta 2, I will be re-testing my plugin.

Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

Dino Azzano — Tue, 02 Jun 2026 12:48:49 GMT

Dear community,

I have a Trados Studio plugin that creates a RibbonGroup in the Home ribbon. This group features 9 buttons.

I have set the sequence in which the buttons should appear in the ribbon by specifying the ZIndex parameter, e.g.

[embed:dc8ab71f-3b98-42d9-b0f6-e21e02a0f8e2:7d9defbd-efb6-4065-b72d-8f5998c095ca:type=csharp&text=%5BActionLayout%28typeof%28ERibbonGroup%29%2C%2010%2C%20DisplayType.Large%29%5D]

The highest index equals to the first position from the left.

This works reliably on Trados 2022 (2022 SR2 - 17.2.10.19084). However, we are now testing Trados 2024 (2024 SR1 - 18.1.3.6657), so I have updated the plugin according to RWS instructions (https://developers.rws.com/studio-api-docs/articles/hints_tips/Update_Plugins/how_to_update_plugins_to_trados_studio_2024_sr1.html?tabs=standard).

Even though no other change has been applied, the sequence of the buttons appears now random. At the very least, it does not respect the ZIndex parameter.

Has anyone experienced this issue and knows any solution?

RE: Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

Robert Cornea — Thu, 13 Aug 2026 09:46:16 GMT

Hi Dino Azzano ,

I've investigated the issue (internal ticket LG-54953) and found the problem. Would you be kind to pick up Studio 2024 CU 5 Beta 2 when it will be released and double check that everything works fine on your end.

Best regards,

Cornea Robert

RE: Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

Daniel García Magariños — Fri, 07 Aug 2026 16:52:50 GMT

Dear Daniel Brockmann , Patrick Andrew Hartnett or Robert Cornea , I am not sure if this is a known issue in Studio 2024 or if it is environmental? Could you reproduce it?

Daniel

Licensing Exception Error when trying to establish an API-connection to Plunet

RWS oneword — Fri, 07 Aug 2026 10:43:44 GMT

At oneword, we are currently testing the automation of Trados projects using Plunet's Trados Project Automation API. However, it seems there is a problem with the verification of our licenses, as the attempt to use them is currently failing. Plunet Support has sent us the following message:

"The error does not seem to originate directly from DeepL or from the paths in the project template, but rather from the Trados license check itself: “Sdl.ProjectAutomation.FileBased.LicensingException”
A valid Trados Studio Professional license is required to use the Trados Project Automation API / FileBasedProject. In this case, the license is apparently being verified, but it is not accepted by Trados in this server/remote/domain environment.
More information here: https://developers.rws.com/studio-api-docs/apiconcepts/projectautomation/overview.html
"Please check whether your Trados Studio 2024 Professional license is authorized for this use."

Our Trados Studio 2024 version is: Trados Studio 2024 SR1 - 18.1.3.6657

Is it possible that there is a problem with our licenses here? We are not familiar with the specifics of the various license types and, unfortunately, cannot assist Plunet Support with this matter ourselves.

Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Daniel García Magariños — Tue, 07 Jul 2026 17:18:13 GMT

This is a continuation of a discussion I opened in the GroupShare developers forum because I think this actually is related to the Studio 2024 API.

community.rws.com/.../connection-to-groupshare-2020-sr1-cu12-not-possible-from-studio-2024-sr1-cu3-with-implicit-windows-credentials---works-if-the-user-explicitly-enters-user-name-and-password

I am beginning to suspect something has changed in the API. The error seems to be coming from this component:
Sdl.Desktop.Platform.ServerConnectionPlugin.TMServer.TranslationMemoryAdminstrationClientFactory.Create(String baseAddress, UserCredentials credentials, IServerConnectionService serverConnectionService)

In Studio 2022, I could connect to our TM Server in GroupShare with this code.

I used the Windows credentials of the current user without having to ask the user to enter them:

private void button1_Click(object sender, EventArgs e)

{
bool blWindowsAuthentication;
blWindowsAuthentication = true;

// Connect with URL and credentials
// TranslationProviderServer tmServer = new TranslationProviderServer(GetUri(txtServerURI.Text), blWindowsAuthentication, "", "");
TranslationProviderServer tmServer = new TranslationProviderServer(GetUri("">https://SERVERNAME"), blWindowsAuthentication, userName: null, password: null);
MessageBox.Show ("Connected");
}

private Uri GetUri(string _serverUri)
{
return new Uri(_serverUri);
}

Now exactly the same code gives this error:

System.NullReferenceException: 'Object reference not set to an instance of an object.'

Here is the stack trace with more details:

Source: Sdl.Desktop.Platform.ServerConnectionPlugin

StackTrace " at Sdl.Desktop.Platform.ServerConnectionPlugin.TMServer.InternalClients.TmServiceRestClientCreator.CreateRestClient(String baseAddress, ClientSettings clientSettings)

at Sdl.Desktop.Platform.ServerConnectionPlugin.TMServer.InternalClients.InternalRestClient..ctor(String baseAddress, ITmServiceRestClientCreator restClientCreator, IBcmToTransUnitConverter bcmToTransUnitConverter)

at Sdl.Desktop.Platform.ServerConnectionPlugin.TMServer.TranslationMemoryAdminstrationClientFactory.Create(String baseAddress, UserCredentials credentials, IServerConnectionService serverConnectionService)

at Sdl.LanguagePlatform.TranslationMemoryApi.TranslationProviderServer..ctor(Uri serverUri, Boolean useWindowsAuthentication, String userName, String password)\

at WindowsFormsApp1.Form1.button1_Click(Object sender, EventArgs e)

Could somebody test the code below and confirm that implicit Windows Authentication works for them? 

According to the SDK, this should work:

https://developers.rws.com/studio-api-docs/api/translationmemory/Sdl.LanguagePlatform.TranslationMemoryApi.TranslationProviderServer.html
useWindowsAuthentication

Whether to use Windows authentication. When n set to false, userName and password have to be specified. When set to true , either pass null for userName and password in order to log on as the currently logged on Windows user, or set userName to a domain-qualified Windows user name and password to the matching password to log on using basic Windows authentication.

Thanks!

Daniel

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Robert Cornea — Fri, 17 Jul 2026 11:33:23 GMT

Hi Daniel García Magariños ,

The timeline currently is at the start of September.

Best regards,

Robert

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Daniel García Magariños — Thu, 16 Jul 2026 22:51:25 GMT

Thanks for confirming, Robert Cornea ! Do you have already an estimated release date for CU5?

Daniel

RE: Trados Studio 2026: Activating a file already open in the Editor does make it the active file

Daniel Brockmann — Mon, 13 Jul 2026 13:48:20 GMT

Hi Josep Condal - just as an update, we are tracking this as LG-54585 and have put it in scope of the first cumulative update in Trados Studio 2026 Release (timing TBA, tentative August/September). Thanks, Daniel

Trados Studio 2026: Activating a file already open in the Editor does make it the active file

Josep Condal — Mon, 06 Jul 2026 12:08:42 GMT

In Trados Studio 2026 build 19.0.0.3043, when we try to make active an already opened file in the editor different than the one that is already active, the active file is not changed, that is, the call to EditorController.Activate(document) is ignored.

We also noticed the event hook EditorController.Opened is not firing the functions that subscribed to it (unlike the EditorController.Opening event hook that fires them fine).

This issue of the active file not being replaced is also reproducible in the Trados Studio 2026 UI with these steps:

In a Trados Studio 2026 with no files opened in Studio, go the Files view of a project and double click on any file to open it. (This works fine: the Editor view opens, and shows the file double-clicked file).
Go back to the Files view and double click on a second file, different from the first one. (This works fine: the Editor view opens, and has the second file as the active one).
Go back to the Files view and double click again on the first file. (This fails: the Editor view opens, but the second file is the active one instead of the first one).

Just for the record, none of the above behavior happens Trados Studio 2024. In step 3, Trados Studio 2024 correctly activates the first file. Also, in Trados Studio 2024 the EditorController.Opened event is fired and EditorController.Activate(document) is honored.

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Robert Cornea — Mon, 13 Jul 2026 13:05:12 GMT

Hi Daniel García Magariños ,

We are aware of this issue and will be fixed in Studio 2024 SR 1 CU 5 and it's already fixed in Studio 2026.

Best regards,

Cornea Robert

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Daniel García Magariños — Thu, 09 Jul 2026 10:10:28 GMT

Dear Robert Cornea ,

Also FYI, this code also does not work anymore when trying to publish a project to GroupShare Project Server:

project.PublishProject(
serverAddress,
true,
"",
"",
"/testorg",
null));

It only works if the credentials are included explicitly but it does not work if I try to use the implicit credentials. Studio 2022 works fine.

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Daniel García Magariños — Wed, 08 Jul 2026 13:30:14 GMT

Thanks, Daniel Brockmann ! Hopefully there will be a workaround from the API, because it works from Studio 2024 itself.

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Daniel Brockmann — Wed, 08 Jul 2026 12:06:09 GMT

Tagging Robert Cornea around this. We did migrate to REST where we had WCF before so that might be behind this, but just a wild guess.

RE: Do the implicit Windows Credentials work with the Studio 2024 SR1 CU4 API? For me it only works if I explicitly include the user name and password.

Daniel García Magariños — Wed, 08 Jul 2026 11:45:53 GMT

A quick test on the exaclty the same environment (to exclude any possible technical glitches with the Windows credentials) confirmed that the issue is in Studio 2024.

With everything being equal, the same code works with Studio 2022 and not with Studio 2024 SR1 CU3 & CU4.

The test was against the same GroupShare Server (GS: 15.1.12.14175 - GS 2020 SR1 CU12) and in the same Windows Domain (to exclude possible environmental differences).

In the GroupShare forum, they mentioned that nothing has changed from their side and it must be something in Studio 2024.

The stack trace suggests that the connection with the API is building a REST connector. I don't know if that's different from Studio 2022 but the GroupShare REST API requires explicit credentials but latest versions might be different as they added the possibility of using SSO.

It would be great if somebody could confirm whether it should work or not.

Daniel

RE: Trados Studio 2026: Activating a file already open in the Editor does make it the active file

Patrick Andrew Hartnett — Mon, 06 Jul 2026 15:01:58 GMT

Hi Josep Condal ,

Thank you for the detailed report, this is now confirmed. We've reproduced everything you described on Trados Studio 2026 (build 19.0.0.3043), both through the API and through the UI steps you listed (opening a file from the Files view a second time does not make it the active file in the Editor).

To help with triage, we put together a minimal example plugin and can confirm three related symptoms, which all look like they share the same root cause in the EditorController's internal document management:

EditorController.Activate(document) is not honored. In our tests the requested document actually becomes active for a second or two and is then reverted to the previously active document ; so the activation is being undone internally rather than ignored outright. The same reverting behavior is reproducible UI-only via your Files view steps, with no plugin code involved.
EditorController.Opened never fires. Opening fires as expected, Opened does not ; confirmed with per-event counters in the sample plugin (e.g. Opening: 3, Opened: 0 after opening three files).
EditorController.GetDocuments() returns a list of null entries. The list has the correct count, but the entries are null, which makes it impossible to obtain document instances to pass to Activate(document). As a workaround we're capturing the document instances from the ActiveDocumentChanged event instead.

All three behave correctly in Trados Studio 2024, so this is a regression in 2026.

The reproduction sample is available in the Sdl-Community repository on the Studio_2026 branch under Code samples/CustomViewExample ; it includes ribbon actions that demonstrate each of the three issues with diagnostics in the message boxes and trace output.

+ Robert Cornea , Daniel Brockmann ; tagging you to get this triaged; given it also affects the built-in Files view behavior (not just the public API)

How to predefine Selected Fields settings for dynamically added server-based MultiTerm termbases during project creation?

Sophia Wessin — Thu, 25 Jun 2026 15:38:57 GMT

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

RE: Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

Dino Azzano — Thu, 25 Jun 2026 13:52:44 GMT

Hi Mike, first of all, thank you for your reply.

I need some clarification: I assume that the compiled Action ID is the ID passed when defining the Action attribute. So, the first button to appear can be e.g.
[Action("01_LaunchAction", Icon = "Launch")]

However, this does not do the trick in my ribbon. Is maybe my assumption wrong and another ID is meant?

RE: Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

mike zhang — Thu, 25 Jun 2026 09:32:28 GMT

Hello, I have expeirenced the same problem and worked it out.

2022 is Zindex, and 2024 is sorted alphabetically by compiled Action ID, please refer to my buttions, same order in 2022 and 2024.

You need to add prefix like mine:

Button	Source ID	Compiled ID	Order
Term Extraction	`AIHub_01_ExtractTermsFileViewAction`	Identical	700
AI Translation	`AIHub_02_TranslateFileViewAction`	Identical	600
AI Review	`AIHub_03_ReviewFileViewAction`	Identical	500
AI Quality Check	`AIHub_04_QualityCheckFileViewAction`	Identical	400
Remove @ Sign	`AIHub_05_RemoveAtSignFileViewAction`	Identical	300
Bilingual File	`AIHub_06_GenerateBilingualFileViewAction`	Identical	200
Settings	`AIHub_07_SettingsFileViewAction`	Identical	100

Note: The first 6 names in the "Button" column are translated from Chinese for reference only — the actual Action IDs embedded in the compiled plugin are the strings shown in the "Source ID" column, which are identical to the "Compiled ID" column.

RE: Sequence of buttons on ribbons no longer kept after upgrading plugin from Trados 2022 to Trados 2024

Dino Azzano — Tue, 16 Jun 2026 08:40:10 GMT

Since the issue persists, I would like to bump this question.

Does Trados 2024 API support parallelization?

Stelios Mathioulakis — Fri, 12 Jun 2026 08:03:56 GMT

Hi all,

Is parallel use of FileBasedProject and FileBasedTranslationMemory from multiple processes on the same machine, under the same Windows user, a supported scenario in the Studio 2024 SDK? I know this worked in previous versions but in one environment that I use 2024 I get the errors below when more than 1 worker is invoking my .exe at the same time:

The translation memory data file engine returned an error:
attempt to write a readonly database

The translation memory data file engine returned an error:
disk I/O error

The per-task projects and .sdltm files are in separate folders, so they don't collide on disk. These parallel executions all have different target languages, so there should not be any collision in theory.

So, has something changed in Trados 2024 in regards to running in parallel? Thank you

How to convert .sdlftsettings into .sdltpl?

Stelios Mathioulakis — Wed, 10 Jun 2026 13:26:00 GMT

Hello all,

Is there a standard way to turn an exported file type settings file (.sdlftsettings) into a project template (.sdltpl)? Ideally via the Project Automation API, rather than hand-editing the XML. Thanks!

RE: How to convert .sdlftsettings into .sdltpl?

Andreas Galambos — Thu, 11 Jun 2026 14:11:20 GMT

The constructors in C# can only create project based on existing templates. So the normal approach would be to create all required project templates first.

However, you are talking about the one and same project needing different fiel type settings depending on the workflow?

Changing file type settings in the midst of a project is not something I would ever have considered. Do you need to replace one setting by a different one during translation?

If not, I would simply add all required settings into that one project template. If you actually need to replace or dynamically add a setting while the project is already in production, you are in for a treat.

You will have to work around the API. Unload the project, manipulate the sdlproj file itself, then reload the edited project.

First you will have to clone this node from the sdlftsettings:

...and in the sdlproj file, create a new "FileTypeManagerConfigutationItem", with child "<Enabled>True</Enabled>", and insert the cloned node with namespace prefix "d3pl":

...and then some more, as you still need the settings themselves. Best you create a simple template, then one with the setting imported, compare the two to find the nodes you need.

Best regards,

Andreas

RE: How to convert .sdlftsettings into .sdltpl?

Stelios Mathioulakis — Thu, 11 Jun 2026 12:46:52 GMT

Thank you for your reply. The problem is that, to my knowledge, the .sdlftsettings can't be passed to the project object of the Trados API in C#. The contructor can only use an optional path pointing to a .sdltpl file. So, in my case my .sdlftsettings can change on each workflow execution, so the manual approach can't work. Do you have a solution for this or am I missing something regarding the API specs? Thank you.

Efficiently Loading Large SDLTB Termbases

Helena Grulichova — Tue, 01 Jul 2025 06:47:54 GMT

Hi all,

I'm looking for the most efficient way to load a large number of entries from a MultiTerm .sdltb termbase using the COM API.

Currently, my code looks like this:

This approach works fine for small termbases. However, with 100,000+ entries, GetEntryIDs() never completes—it just runs indefinitely.

Is there a better approach, or even a way to access the entries directly from the .sdltb file without going through the COM layer?

Any tips would be greatly appreciated!

Thanks,
Helena