• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 999 views
  • Users 0 members are here
Options
Related

Custom Field value replaced instead of added

Caroline Mongeau

I created a TM called "Paperback" with a custom field "File Code" which is defined as Text (Multiple).

Paperback already contains the following unit: "Once upon a time, there was a rabbit named Cookie" and the translation was assigned the value "Code = C804".

Using Paperback, I translate a second file containing the same sentence. The Code for this new file is "C912". I confirm the sentence found as it is already properly translated. But going back to the sentence I just finished confirming, I can see that the translation unit now shows "Code = C912" and not "C804, C912" as I should expect, "Code" being defined as Multiple.

I do not encounter this behavior with every project or every TM. It must depend on a specific option or group of options that are checked or unchecked somewhere, but going through the different groups of settings, I can't find which option is faulty. 

I work with SDL Trados Studio 2021 Freelance 16.0.1.2917. A very similar (the same?) question was posted but never really answered: https://community.sdl.com/product-groups/translationproductivity/f/studio/19855/tm-fields-updating. Any hint would be appreciated!
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi

    Thank you for your clear explanation.

    In order to try understand the randomness, please clarify if you use project templates or do you always translate as single document.
    Also how old are your TM's meaning, where they created all in 2021 or could it be some are from legacy versions?

    I was able to reproduce the same translation against both codes  C804 and C912

    Screenshot of Trados Studio project settings showing a list of translation memory and automation settings with no visible errors.

    Below I captured how my working example has been setup to see if you can spot differences on your end.

    TM:

    Screenshot of Trados Studio project template settings displaying 'Name' and 'Value' columns with two entries: 'Sort Methodology' and 'File Codes'.

    *legacy TM's would have a different layout when it comes to this

    Project settings:

    Screenshot of Trados Studio showing a dialog box for translation memory attributes with 'Field' and 'Value' columns, including an entry for 'File Code' with values 'C804' and 'C912'.

    I hope the screen prints helps and if not, perhaps you can clarify the 2 questions I asked above.

    Kind Regards

    Lydia  

    Lydia Simplicio | RWS Group

    _______
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 4:06 AM (GMT 0) on 29 Feb 2024]
  • 0 in reply to Lydia Simplicio

    Hi Lydia,

    Thank you for looking at my post and sorry for not being back sooner -- terrible, terrible floods in my area! 

    To answer your questions : I never translate as a single document, even when a project contains only one document. Today I encountered the problem with a TM created in 2017.

    Here are the settings for my TM:

    Screenshot of Trados Studio Translation Memory settings with an arrow pointing to the 'Concordance' option set to 'Yes'.

    And here are the settings for my project:

    Screenshot of Trados Studio project settings showing 'Value' column with 'Origin' set to 'TM' and 'Value' set to '100%'.

    This new project has a sentence already translated in our File 18-062 (about one year ago):

    Screenshot of Trados Studio project with a translated sentence highlighted in orange, indicating a match from TM, and a warning symbol in the status column.

    ...and this is what the sentence looks like now that I reused the sentence:

    Screenshot of Trados Studio project with a translated sentence highlighted in orange, indicating a match from TM, without any visible errors or warnings.

    I seems to me that my project settings are OK. Could this problem be caused by my using more than one TM? There are two TMs attached to this project.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 4:06 AM (GMT 0) on 29 Feb 2024]
Reply
  • 0 in reply to Lydia Simplicio

    Hi Lydia,

    Thank you for looking at my post and sorry for not being back sooner -- terrible, terrible floods in my area! 

    To answer your questions : I never translate as a single document, even when a project contains only one document. Today I encountered the problem with a TM created in 2017.

    Here are the settings for my TM:

    Screenshot of Trados Studio Translation Memory settings with an arrow pointing to the 'Concordance' option set to 'Yes'.

    And here are the settings for my project:

    Screenshot of Trados Studio project settings showing 'Value' column with 'Origin' set to 'TM' and 'Value' set to '100%'.

    This new project has a sentence already translated in our File 18-062 (about one year ago):

    Screenshot of Trados Studio project with a translated sentence highlighted in orange, indicating a match from TM, and a warning symbol in the status column.

    ...and this is what the sentence looks like now that I reused the sentence:

    Screenshot of Trados Studio project with a translated sentence highlighted in orange, indicating a match from TM, without any visible errors or warnings.

    I seems to me that my project settings are OK. Could this problem be caused by my using more than one TM? There are two TMs attached to this project.
    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 4:06 AM (GMT 0) on 29 Feb 2024]
Children
No Data