Monday, November 20, 2017

Sharepoint and alternate languages

So what happens when a column is created and then changed.
And then, possible, changed again in an alternate language?

First created, staticName is set and the cultured name
image
When names is changed, only the culturename is changed
clip_image001
When and alternate language is added, and copy of the culturename appears.
image
When name is changed again to doktor2, only the current language version is changed. Swedish 1053.
clip_image001[6]
Now we have 3 version to manage.
When we choose overwrite language specific version the values dont change.
clip_image002
When we now change the column to Doktor3, only the 1053 version change when we’re using the alternate languagebrowser.
clip_image003
But if we change using the default language (1033) to doktor4, all local variants are overwritten
clip_image004
But then a local editor is at it again, setting doktor5 in swedish and the values are off.
clip_image005
But what happens if we now remove local variants? Then we're down to only the default columns
clip_image006
Changing from swedish gui to doktor6 and the english 1033 is changed.
clip_image007
But what happens if language is enabled again? Well, the old value is still there…
clip_image008
The lesson here?
Stay away from alternate languages!
And also a fun script for checking all the versions of a fields on a list.


No comments:

Powershell and Uptimerobot

Uptimerobot can be quite tedious when you need to update many monitors at once. For example say you bought the license for Uptimerobot and n...