KB37902: After a configuration object is renamed, using a MicroStrategy Developer 9.x or 10.x machine configured to use an interface language different than the metadata's default, the object is not renamed and instead a new object translation is saved.

SYMPTOM:
After renaming a configuration object, users may notice that not all other users can see the new name, and that they continue to see the original object name. The user who changed the object name and the users who see a different name are using a different interface language. This setting, is shown in the screenshot below:
 

 
CAUSE:
 
This scenario can be reproduced when the user who changes the object name has a Desktop interface language which is different from the metadata's default language. When this user changes the object name, he is actually entering a translation in the language he uses in his interface. This can be confirmed by checking the Translation Editor for the object.
 
This behavior is correct. Strategy 9.x has a feature known as metadata internationalization. As part of this feature, a Strategy 9.x metadata contains a set of languages by default to promote multilingual systems. Each metadata has a default language and may or may not have additional languages. When more than one languages are present the object gets named in the language in which it was modified.
 
This behavior can be prevented by going to Languages Manager, which is a Configuration Managers, and deleting all languages except for the default language. The Languages Manager is shown in the screenshot below:
 

 
Before doing this, users should make sure all administration objects have their names in the default language and no translations. This will not have any adverse effects in projects that are intended to have only one language, and the result is that the project will not have any metadata internationalization functionality. After doing this, anything modified (renamed, or created in any locale) in Administration will only impact English.
  
WORKAROUND:
 
Another workaround, if deleting all non-default languages is not desired, is for the user who is renaming the configuration object using a Desktop machine with a different interface language, to rename the object through the object's Translation editor and changing the object name string in the default language.