You are currently working on UAT 

x-ConfirmationLevel in TMX

Hi,

I'm curious as to why this property is in the TMX export from Studio 2019 seeing as it doesn't seem to update properly or be accessible in the editor. In the bilingual file, the status of a segment was confirmed as ApproveSignOff, apart from the change in status no other change was made to this segment. The translation memory was upated with Update Main Translation Memories batch task. The usage counter is incremented for the segment but the property remains as <prop type="x-ConfirmationLevel">Translated</prop> and not <prop type="x-ConfirmationLevel">ApproveSignedOff</prop>as I would expect.

Could someone explain why this happens? I see others have already commented on this mystery property.

https://community.sdl.com/product-groups/translationproductivity/f/studio/9159/tu-status-information

Thanks,

Daniel

Parents
  • @krupaadrian

    Not sure why you deleted your post. I'm trying to clean up a groupshare TM which has been updated incorrectly over some time with around 170,000 segments and work out whether the custom fields in the TM are having a negative impact on TM leverage. Unfortunately the most recent TU is not always the correct translation. I don't think it would be a good idea to use SQL directly on the server TM, I'd rather work on a copy offline so TMX > sdltm is unavoidable. I like your approach using sqlite for source inconsistencies in your plugin - but how could I achieve the same for target inconsistencies ordering the most recent first for viewing inconsistencies and how could I delete them? Do you have suggestions of SQL statements that have worked for you that I could use in DBrowser for sqllite? I can provide more info offline if you can help.

Reply
  • @krupaadrian

    Not sure why you deleted your post. I'm trying to clean up a groupshare TM which has been updated incorrectly over some time with around 170,000 segments and work out whether the custom fields in the TM are having a negative impact on TM leverage. Unfortunately the most recent TU is not always the correct translation. I don't think it would be a good idea to use SQL directly on the server TM, I'd rather work on a copy offline so TMX > sdltm is unavoidable. I like your approach using sqlite for source inconsistencies in your plugin - but how could I achieve the same for target inconsistencies ordering the most recent first for viewing inconsistencies and how could I delete them? Do you have suggestions of SQL statements that have worked for you that I could use in DBrowser for sqllite? I can provide more info offline if you can help.

Children