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

xtensibilitybro's avatar
xtensibilitybro
New Contributor III
3 years ago
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...
Application Properties
Methodology
  • ChrisLoran's avatar
    ChrisLoran
    3 years ago

    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's avatar
ChrisLoran
Icon for OneStream Employee rankOneStream Employee
3 years ago

In a nutshell:
These will all fail, if the calculation is invoked by a user that has a non-English culture setting:

'-- Bad , never do this... --
Dim somePrice As Decimal = 123.45
api.Data.Calculate("A#Result = A#Qty * " & somePrice)

also this is a big no-no , for the same reason

Dim somePrice As Decimal = 123.45
api.Data.Calculate( $"A#Result = A#Qty * {somePrice}" )

And so is this:

Dim somePrice As Decimal = 123.45
api.Data.Calculate( String.Format("A#Result = A#Qty * {0}", somePrice ) )

 All three examples above will either produce a runtime error, or cause incorrect calculation results, when the calculation is initiated by a user with a non-English culture setting (where their local reporting uses comma as the decimal instead of dot).