The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.
Forum Discussion
Solved
Adding Cultures after Go-Live
Hi All,
I was wondering if anyone had experience adding cultures to an applicaiton after go-live. Considering this is a system wide change its difficult to test without applying across all applicat...
This is similar to an existing enhancement request PF-26868.
Unfortunately you can't add custom culture codes ( well, you can in the server config, but they won't actually appear in the application unless they are one of the standard culture codes as set my Microsoft )
If it is only a few variations of descriptions, then you could use some other "English" culture codes like en-AU, en-CA, en-CB, en-IE, en-NA, en-GB, en-ZA , and get your cube views to display the correct one depending on the entity.You could of course do something more custom, using XFBR/BRString in the :Name override in the Cube View Rows/Columns, but then this won't work so well if you are using member expansions like A#BS.Tree, A#PL.Descendants. A DynamicCalc on the V#Annotation (or other text-based view member) could also be used to show alternate descriptions based on some lookup logic, but will probably have a negative impact on performance.
JackLacava
OneStream Employee
OneStream EmployeeThat documentation warning is generic. Basically, if you modify app server settings with the utility, they all get saved in a single file in one go; so if you went in to modify cultures and by accident deleted a database connection while doing so, you'd be screwing up your environment.
Adding cultures, by itself, is a relatively safe operation; the only real gotcha from a performance perspective is what ChrisLoran mentioned. I'm writing a blog post on techniques to address that point, stay tuned š
Other bits that might be affected: if you provide localized descriptions for some of your metadata members but not all of them, your cube views and dashboards might end up showing a mixture of languages, which is not a good look from a professional perspective - so plan for that (i.e. do all the work in dev, then load updated metadata in prod as soon as you enable a new culture).