Studio 2019: Updating SDLX TMs

Question

I have a client who still prepares idt files, which I process in Studio. This is not a problem in Studio 2019. 
 For each project, they also provide me with a SDLX translation memory in the mdb format. 
 In previous Studio versions, it has been unproblematic to run these files through "Upgrade Translation Memory" in the Translation Memories view. 
 With Studio 2019, however, I have been unable to use this function. 
 The first step of the process, "Export" is successful, but for the second, "Create translation memory", I get "TextContextMatchType must be specified" (whatever that means). 
 For the third step, "Build Translation Model", I get the dreaded "Object reference not set to an instance of an object", which is probalby du to the second step error. 
 For some reason, the last two steps are "completed", but that is no use, because the sdlxliff TM output during these steps are empty. 
 As far as I know, the client is not doing anything differently. 
 Hope someone can help, especially since SDLX is also an SDL product. 
 All the best, 
 Jon

Jon Kittilsen · Accepted Answer

Since I started this thread, I am happy to report that the issue was fixed with the last Studio upgrade.

Paul Filkin · Answer

Hi Jon Kittilsen 
 Jon Kittilsen said: Hope someone can help, especially since SDLX is also an SDL product. 
 Not exactly! SDLX was discontinued a very long time ago and I have not heard of anyone still using it for a long time. Can you share one of the SDLX translation memories you are trying to upgrade?

Paul Filkin · Answer

Hi Jon Kittilsen 
 No, it hasn't worked. Try using this method:

Jon Kittilsen · Answer

4846.ProjectTM_JobNo62394EN-US_NO-NO.mdb 
 OK. Tried that. File hopefully attached. 
 
 Jon

Paul Filkin · Answer

Thanks Jon Kittilsen 
 
Lucky and unlucky... I got the file but it looks like a bug in 2019. I had no problem using 2017 (which I presume you have access to so have a workaround?). I have logged this with support to reproduce and log a bug with the development team. 
 
Regards 
 
Paul

Paul Filkin · Answer

Hi Jon Kittilsen Just confirming that this is a bug and it's logged as CRQ-10932 just for your information. Will be easier to follow up on by referring to this number. 
 There is also a workaround which is to take the TMX file that still gets created in the TEMP folder and then upgrade that. So even if you don't have access to 2017 there is a way around it. Of course if you still have a copy of SDLX then just export to TMX in the first place and life is easier :-)

Trados Studio > 1. Trados Studio

Studio 2019: Updating SDLX TMs