Support for localized formats

Field data is stored using various data types. When using a non-US computer, or when the region is set to a non-US region, data stored in numeric and date fields are correctly displayed in the local format. These fields also accept input in the local format. For example, when the region is German (Germany) or the machine is a German version of Windows, you can enter a Demand Order Time of 28.09.2016. The Model Culture setting on the General tab in Model Settings establishes the expected default formats for numbers and dates.

Many fields that accept numeric values are actually stored in text fields. This is to support additional features such as input pipes, distributions, units of measure and step costs. The solvers expect input in US format, so local formats are resolved during the input generation.

In general, expressions and dates can be entered using the local format. When using the comma as the decimal character, there are some considerations for specific expression formats. The table below lists some examples of expression formats using the comma vs. the period as the decimal character:

Expression format Period as decimal example Comma as decimal example Notes
Numbers 1234.56
1,234.56
1234,56
1.234,56
1 234,56
Use of digit grouping symbol is optional.
Step Cost <0,100.5><15.5,125.5> <0|100,5><15,5|125,5> Use | in place of , to separate Value and Step values. You can also use the semi colon (;).
Units of Measure, such as Time 1.5 HR 1,5 HR  
Distributions N(10.5,3) N(10,5;3) Use ; in place of , to separate values.
Book Value <10000.5|9875.5|9250> <10000,5|9875,5|9250>  
Quantities in the Forecasts table 15.5,17.25,35.5,21.75 15,5;17,25;35,5;21,75 Use ; in place of , to separate values.

Last modified: Wednesday May 15, 2024

Is this useful?