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.
ChrisLoran
OneStream Employee
OneStream EmployeeAdding culture codes doesn't directly affect performance, but it may cause business rules (and possibly some Marketplace solutions) to stop working suddenly, if a user with a non-US culture code logs in and runs consolidations.
If you have any calculation formula/rules that try to append a Decimal variable to a calculation string, and you don't explicitly state the Invariant culture in the calculation, then these calculations will certainly fail for any non-US users.
There is still a big myth out there that just because the calculations may be running on a server in the US, that culture code settings only affect the front-end view/reporting output etc. I wish that were true, but it's not.
The danger is not adding culture codes after go-live. The danger is assigning an active user to a non-US culture code, and having them run calculations/consolidations, unless the rules are checked and double-checked to work properly when initiated by such users.