Translated Name / Field - Why is it getting added to update sets?

[Sooriya3]

Hi

Why are Translated Name / Field getting added to update sets? How do I disable this? When I move from DEV to UAT though there are no clashes when I run the preview, the variables with choices are not getting moved.

I have one named environment with 5 options and those are missing in UAT when I move from dEV. Other questions and workflows move across without any issues. Just this variable named "environment "and another variable named "type of request". Both have drop down options which are not getting moved across to UAT.

[Ankur Bawiskar]

@Sooriya3 

the records get captured in update set due to the update_sync=true attribute in Collection type field

Also sometimes when you view the choices etc in other languages then platform might be creating entry into that table automatically.

This is because of the system property "glide.translate.learn "

-> You can manually review the update set and remove the unwanted ones.

-> see if the choices are captured correctly in your update set

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Sooriya3]

Not sure why this is ONLY impacting some variables as listed above.

[Ankur Bawiskar]

@Sooriya3 

I already shared the complete details.

If my response helped please mark it correct and close the thread so that it benefits future readers.