Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
I am currently upgrading a Studio plugin from Studio 2015 to Studio 2019.
One part of the plugin consists in importing an SDLXLIFF file in a Groupshare TM. To do so, I used to use the ScheduledTranslationMemoryImportOperation constructor where I would have used the following methods (in the following sequence) to load the import operation on the server:
Create: to create the import operation
Upload: to upload the import file
Queue: to queue the instance of the import operation.
With Studio 2019, it seems the constructor ScheduledTranslationMemoryImportOperation does not exist anymore in the Sdl.LanguagePlatform.TranslationMemoryApi namespace. However, there seems to be a new constructor which might replace the above-mentionend constructor. It is named ScheduledServerTranslationMemoryImport.
My questions are:
1. Does the ScheduledServerTranslationMemoryImport constructor replace the ScheduledTranslationMemoryImportOperation? I can't see any trace of this new constructor in the documentation
2. Apparently, the new constructor has no "Create" and "Upload" methods. Which methods should be applied? Does the "Queue" method cover both the "create" and "upload" process?
Thank you in advance for your support.
After the import.Queue() method, you need to evaluate importer status and refresh the importer. importer.refresh(). Please refer to below trados-studio-api sample.
Dear Community members, Paul,
I still haven't found a solution to the above-mentioned problem. Anyone to help me on this one?
Hi Laurent Pierret
I asked the team to look at this when they complete the work they're doing at the moment. Hopefully not too long...
Thank you for following up.
Hi Laurent Pierret,
Queue method does not cover create process.
You can use the following code to upload an xliff to an existing server tm:
var uri = new Uri(@"uri");
var translationProviderServer = new TranslationProviderServer(uri, false, "user name", "password");
//Import to existing tm var guid = new Guid("Existing TM Guid"); var tm = translationProviderServer.GetTranslationMemory(guid, TranslationMemoryProperties.None); var langDirection = tm.LanguageDirections;
var import = new ScheduledServerTranslationMemoryImport(langDirection); import.Source = new FileInfo(@"path to xliff"); import.Queue();
Thank you for your reply and sorry for my late reaction. I was quite busy last week.
I will have a deeper look at what you suggested but at first glance, I exactly implemented as you did and I received an error message stating that the path could not be found. As I said, I will check again and come back to you.
I am following your code step by step, but when the code reaches import.Queue(), the method never returns. On the GroupShare server I can see that the scheduled import operation has finished successfully, but in my code I can never get past import.Queue(). Is there anything I am missing?
Using Studio 2021 ver 18.104.22.16817. Is this a bug that may be fixed in CU4 ?
Another alternative for importing into server based TM is using GroupShareKit. TranslationMemoriesClient has ImportTm method.