It is a known problem with Documentum Composer that it uses the locale of the underlying OS to set its default locale when creating project.
For example, my machine's locale is set to nl but that doesn't mean all the Documentum Content Servers I develop for are nl aswell... Most Content Servers are plain old en.
When trying to install a project on a Content Server that only supportsen when Composer's locale is not en, you will come across the following message:
When searching for a fix for this issue on the internet, or even specifically on the EMC Community Network, all you get as an answer is to manually change the nls_key="nl" value to nls_key="en" for all affected artifacts. This is alot of work, especially because you have to change it for every attribute for every object type.
Plus, after you have done this, you will most likely receive errors inside some parts of Composer because of your manual actions.
Example: trying to access the Value mapping tab of an attribute after you changed the nls_key in the XML yourself will throw the following exception:
So, not a great workaround...
Whenever you create a project with Composer it generates a .dmprojectfile inside the project's rootfolder. This is an XML containing some default values for Composer. And yes, you guessed it correctly, it also stores thedefaultLocale value.
The file looks something like this:
If you change the value of defaultLocale to en and restart Composer (refreshing your project apparently isn't sufficient) the problem is gone!
Please contact us to help you with your digital journey
Enter your email address below to have a digest of our featured blog posts sent to you