Forum Discussion
Challenges with multilingual fields in SharePoint
The order in which you do things matters, and this bug has existed for about a decade. You have to translate the site column MUI before you add the content type to the list, any MUI changes done after that are not inherited by the list.
In the image below, I have created 3 site columns "Add before", "Add after", and "Translate after". I translated "Add before" and added it to the content type, then added the content type to the list. Then I translated "Add after" and added both "Add after" and "Translate after" to the content type. Then I translated "Translate after". This is the result:
Only the translation that was done before adding the content type to the list is relfected in the list. This is because this is not true inheritance. The columns are copied to the list at the time the content type is added. These columns get updated when certain properties of the ancestor column is changed, but that does not include changes to the MUI translations. You can re-translate the column name manually in the list itself.
Hi Martin,
Thanks for your response.
I did some further tests and I think that there is a general issue.
Whenever I create a website column, the translations will not be pushed to the SharePoint lists. That means, that I can also reproduce the behavior when I translate the column before adding it to a content type and to a list.
The site content type looks as expected. The list content type only shows the English translation.
Do you also know this behavior? Is there a way to reconnect the list content type to the site content type?