Tom Imhof said:

Hi, originally, I posted this question here

 Exporting a Server TM using the TranslationMemory API results in a TMX file that misses the context matching information 

Hi Tom Imhof , I have reviewed this issue today, but unable to reproduce the issue that you are reporting.

Prerequisites

• Trados Studio 2022 SR1 - 17.1.6.16252
• GS: 15.1.9.12529 - GS 2020 SR1 CU09

Steps

1. Create a server based tm from GroupShare
2. Open the server based TM in Stduio & add some custom fields
3. Add a few TU entries & assign a custom field value to one or two of the TU's
4. Commit changes so that they are updated on the server.
5. Create a standalone app to connect and export the server based TM to tmx
   1. Documentation: How to export serverbased TM to TMX

Actual result

The custom field values are exported correctly, visible from the TU's in the TMX that was exported from the serverbased TM

Follow up

Tom Imhof  Can you pls provide the GroupShare version + Trados Studio version you are using?

Dear Patrick, 

many thanks for your answer. My issue is about the *context matching information* - not about custom fields. Custom fields - I agree - do survive the export. The context matching information in the TM is stored in these fields:

<prop-type="x-IncludesContextContent">True</prop>

This turns the feature on, I guess.

Then on segment pair level, you will find:

<prop type="x-Context"> etc. as highlighted in the screenshot:

These elements - when you export via the API from a server TM - are *not* exported. I am quite sure you can repro it. I tested against an older GS 2020 SR 1 CU7 (gsdemo.gs.sdl.com) as well as my own VM running GS 2020 SR1 8.1. I will test against CU9 as well, but I am quite sure it is not a Groupshare issue - it is a Studio API issue. 

Hi Tom Imhof , you're absolutly right, I missread this initially; thx for additional info

I'll review again (this time setting up the context match information, e.g. previous segment...) & confirm your findings before I escalate it to the development team. 

Perfect! Many thanks Patrick!

Hi Tom Imhof ,  I have just tested this again, this time preparing a TM with context match information.  The result however confirms that it is working as expected.  Can you test against CU9, so that we are comparing apples with apples?

This is an export from the same automation code I used for the first review:

Note: It includes the x-ContextContent context match information.

Hi Patrick,

ok, I will test with CU9 then and report back - it would be wonderful if it was fixed already in CU9  

Hi Patrick,

my test with CU9 was negative - with CU9, this code causes an internal server error (500) - it is still working fine against CU7 and CU8.1 of Groupshare (running Trados Studio 2022 SR1):

>>>>>>>>>>

Public Function GetServerTMs()

Dim ServerUri As New System.Uri(ServerURL & ":" & Portnumber)

Dim TMServer As New TranslationProviderServer(ServerUri, False, Username, Password)

For Each ServerBasedTranslationMemory In TMServer.GetTranslationMemories().   <---- Internal server Error (500) happens here 

Dim ServerTM As String = ServerBasedTranslationMemory.Name

Msgbox(ServerTM)

Next

Return 0

End Function

>>>>>>>>>>>

However, I will create a separate request for this issue, as this has (I think) nothing to do with my original ticket here.

But fact is - with CU9, I cannot retrieve any TMs any longer using the code above. This code as worked for years without any issues.

Hi Tom Imhof  - there is indeed a known issue in the API when retrieving the list of GroupShare TMs, however you can work around it in your code by making certain small changes. I would ask Andrei Caia  to explain the workaround here when he has time. Also tagging Paul Petrehus . Thanks, Daniel