Detecting language please wait for.......
This happens when you have a very long list.
The really bad thing is, that it also has an impact on Studio 2017 and Studio 2019 when opening a serverbased TM:(
Does anyone have the same problem?
GS 2020 SR1 is installed on a fresh (three days old) Windows 2012 R2 + SQL 2016 Server with all current Microsoft critical updates (July).
Dear Darius and Roman,It would be best if this gets sent to SDL Support as a case, and they will validate this behavior. I believe a remote session to the affected system is needed - for an accurate replication…
Hi @Roman Kuleshov
You can raise this with the Support team, as we are not sure whether this is confirmed as the Defect CRQ-16505.
This might be related to some other settings and Support needs to investigate…
No, I have not seen this issue on other systems, I just checked my test system and the sorting works fine.
Have you tried clearing your Browser's cookies/cache and trying again?
Can confirm, sorting doesn't work at all with GS 2020 SR1. You can click on any field and the list is still unchanged. And it really doesn't have any comprehensible sorting order in the first place, it's totally random and chaotic.
Tried different browsers and even different PCs.
Dear Darius and Roman,It would be best if this gets sent to SDL Support as a case, and they will validate this behavior. I believe a remote session to the affected system is needed - for an accurate replication. It is possible you both deal with different issues but also, there is a chance this could be something to be raised to SDL Development. I am aware there is also an item raised for SDL Dev, as CRQ-16505 where a specific action in webUI (resources > translation memories) can cause an incorrect sorting.But moving forward SDL support will probably be able to clarify more.Could you please work with SDL Support, by raising a case from your SMA account:https://gateway.sdl.com/apex/communityknowledge?articleName=000001889Hope this helps.Radu
Hello Radu and Roman,
this problem is already confirmed/reproduced by SDL and they will fix that in the next update.
Maybe this problem is triggered by "some" circumstances, don't know.
Thank you, Radu. Since Darius said below that the issue has been confirmed, do we still need to make a case with SDL support?
This might be related to some other settings and Support needs to investigate further.