Forum Discussion
Renaming columns -> new name not showing for site members
Update July 2020:
I still had this issue with new sites and almost gave up on troubleshooting. I had a brainstorm with another SharePoint minded person and it became clear that the language template might be a thing.
When you visit a website, the language in which the browser is set determines the language in which the content is displayed. If the website offers content based on language of course. With modern browsers you have the option to support multiple languages, like spell check and browser interface. My native language is Dutch, but I set my browser to English to read Microsoft Docs in English (the machine translation is absolutely horrible).
Now back to SharePoint. I create a site, make content types and columns, create libraries and lists and all that in my English browser. Most of my colleagues all have browsers with their interface set to Dutch. And here's where things go wrong. All Dutch visitors see the columns in their old ("ugly") name. When I change the user's UI language to English, *poof* all columns are in the correct "fancy" names.
So in conclusion, I have to rename all columns in two different languages, and more if we want to support other languages for our visitors as well....
Thanks ChrisWebbTech.
I tried clearing browser and the shift F5 with a user. I also tried inviting a new user, the same results there. Going to try out your suggestion to change the column name in the content type and to create a new view.
Next on the list of things to try: creating a template of the list and see what happens when I create a new list.
- Deleting the list, creating a new list, adding content types > columns still remain the old names and don't update for other users then myself. In the New > Item form, the metadata fields show the old name as well. This is really frustrating.
- You sure they are going to the exact same list and not another orphaned similar list? It is very odd indeed!
Thanks for thinking along Chris. I submitted this issue to Microsoft. Maybe it's a problem on my end, or I'm doing something wrong.
