Thank you, Paul

There are two users for Adrian Maniu. Maybe you tagged the wrong one, since there has been no reaction. Adrian Maniu/Adrian Maniu, do you think you could help with this issue?

Hello,

This is a defect in Studio logged as CRQ-25970. Currently the development team is still looking into this and we do not have a fix date confirmed.

Thank you, Adrian Maniu. Good to know it is on your to-do-list.

Hi Jesús, 

We've just come across this problem as well. Out of 3 dates for this specific segment, we have two dates in the future; our own date (last modified on) seems fine. Please see the screenshot. 

FYI, we cannot change our local settings to another country as suggested in the KB link mentioned by Luciano below.

I hope this can be fixed, as this impairs using the filtering function for our client's memory to look for a specific project by date. Thanks!

Hi Adrian Maniu ,

I have read the following in the infos of the latest CU for Trados Studio 2021 (CU12):

The date and time property of TM units is now consistently being updated across date and time formats, regardless of the method of creation or update. (CRQ-29503)

Is this related to the bug I found, which is discussed in this thread and logged as CRQ-25970? Is CRQ-25970 fixed?

Hello, 

Both issues are the same, but they have been implemented in different versions: CRQ-29503 was addressed for Trados Studio 2021 CU11 and CRQ-25970 for Trados 2022.

Hi Adrian Maniu , Paul ,

After having updated Trados Studio 2021 tu CU12 for all our users we have come to realize that the issue reported above still persists. Now, however, it is only the "Created on" system field that changes the date format. Units that I create today on a German Windows system are saved to the TM with creation date August 9th. Regardless of whether my Trados Studio client was set to German or English. The TM I used was a GroupShare TM.

Hi Luciano,

Same problem here. The only solution I was given is to update to Trados 2022 :(

See (11) Crazy system fields in Translation Memory - 2. Trados Studio - Trados Studio - RWS Community.

Hi Almudena Ballester ,

It is good to hear, we are not the only ones with this problem. Even though I would't wish it on anyone.

So, judging from what you wrote in the other Community post, you are also having this issue in Trados 2022? Or did you mean that the datetime remains turned around? The latter would be the only logical thing to happen, since the datetime is written into the SDLTM file. The only way to "repair" this, I guess, would be to create a TMX export, identify the wrong time stamps and correct them in a text editor. Of course, this could mean a huge effort.

So, did you test if Trados 2022 writes the correct datetimes into the TMs?