The numeric property type stores simple numerical values. The value is a double precision value in the range of -1.79E+308 to -2.23E-308, 0 and 2.23E-308 to 1.79E+308, and is internally stored as floating point representation (base=2, precision=53).
Numeric properties can be calculated properties.
Display settings
Display setting |
Description |
Unit |
The unit that is associated with the value of the numeric property. Contrary to the quantity property type this unit is only descriptive. The system cannot convert between different units of numeric properties. |
Precision |
Number of digits after the comma that are actually displayed to user. E.g. actual precision can be 5 digits after comma, but in a certain context it may be reduced to 3. |
No grouping |
If set numbers will be displayed without a grouping character, if not set the grouping character as defined in the culture used by the client will be used. |
Hide training zeros |
If set numbers will not show trailing zeros, if not set numbers will always be shown with the number of digits set with the Precision setting |
Validation correction rule |
Defines a rule that can be used by clients to detect valid values and automatically correct invalid values to the nearest valid value. See below for a detailed description of validation correction. |
Table 1: Additionally supported display settings for this property type
Default value
Default value can be any number in the range of - 1.79E+308 to -2.23E-308, 0 and 2.23E-308 to 1.79E+308.
Validation rules
Validation rules |
Description |
Minimum value |
Minimum value that can be stored with this property |
Maximum value |
Maximum value that can be stored with this property |
Table 2: Supported validation rules
Validation correction
Validation correction is a possibility the Client can implement to assist the user when keying in data manually. The validation correction rule that is part of the display settings of a numeric property defines what values are considered as valid values for this property. Values that are not considered will be automatically corrected to the nearest valid value.
Note that as all other display settings the validation correction rule is stored with the property structure configuration but it is enforced by the client. I.e. validation correction is not performed when importing data.
A validation correction rule defines which values or which ranges of values are permitted. In its simplest form a validation correction rule is simply a semicolon separated list of valid values. You may use both point and comma as decimal separator. Do not use grouping characters. Examples:
1;2;3.5;4;9;7
1,3;2.5;5;9;
Instead of specifying discrete values you can also define ranges.
1:4 would allow all floating point numbers ≥1 and ≤ 4
Ranges can be accompanied by a step width. For ranges with a step width the lower and the upper boundary are always valid values, additionally all values between the lower and the upper boundary where (value - lower boundary) % step width = 0 are also valid values.
1:4|1 would allow values 1, 2, 3, 4
1:5|3 would allow values 1, 4, 5
1:2|0.1 would allow values 1, 1.1, 1.2, ... 2
Finally discrete values, ranges and ranges with step width can be comdined:
1;2.2;10:20|2;22:23;
