FSM Mobile Number Element Properties

The following table lists Field Service Management (FSM) Mobile Number element properties, accepted values, defaults, and interactions. It covers the value, min, max, precision, step, stepper, and unit properties.

Property	Accepted values	Default	Interaction and behavior
`value`	Number; numeric strings are also coerced during resource normalization.	`null`	The numeric value stored by the element. For new configuration, use a JSON number literal, such as `1.25`, rather than a numeric string such as `"1.25"`.
`min` / `max`	Number or `null`.	`null`	Defines inclusive validation limits.
`precision`	Whole number from `0` through `8`.	`8`	Limits decimal entry and display when neither a unit precision nor a display precision determined by `step` applies. A value of `0` prevents decimal entry. This property does not add a stored-value validation rule. A unit precision takes precedence. Note: Starting with version 2026.07.2, replace an explicit `"precision": null` with a whole number from `0` through `8` that matches the required number of decimal places. If `null` remains configured, FSM Mobile normalizes it to `"precision": 8`.
`step`	Positive number or `null`.	`null`	Sets the permitted increment for validation and numeric stepping. When no unit precision applies, a whole-number `step` displays zero decimal places, and a fractional `step` displays the number of decimal places in that increment. Use the following `step` values for common increments: `1` for whole numbers `0.01` for cents `0.25` for quarter-unit increments Note: Starting with version 2026.07.2, replace `"step": "any"` with a positive numeric increment, such as `"step": 0.01`, or omit `step` when no increment is needed. If `"any"` remains configured, FSM Mobile normalizes it to `null`, so no increment is applied.
`stepper`	Boolean.	`false`	Shows increment/decrement controls. It works with `step`; it does not change numeric validation by itself.
`unit`	String identifier or `""`.	`""`	Selects a named Number formatting profile from the mobile context's unit collection. A matching profile can set the effective display/input precision and add a prefix or suffix; it does not change the stored number or set `min`, `max`, `step`, `stepper`, or `value`. An unrecognised identifier produces unadorned numeric formatting.

Property

Accepted values

Default

Interaction and behavior

value

Number; numeric strings are also coerced during resource normalization.

null

The numeric value stored by the element. For new configuration, use a JSON number literal, such as 1.25, rather than a numeric string such as "1.25".

min / max

Number or null.

null

Defines inclusive validation limits.

precision

Whole number from 0 through 8.

8

Limits decimal entry and display when neither a unit precision nor a display precision determined by step applies. A value of 0 prevents decimal entry. This property does not add a stored-value validation rule. A unit precision takes precedence.

Note:

Starting with version 2026.07.2, replace an explicit "precision": null with a whole number from 0 through 8 that matches the required number of decimal places. If null remains configured, FSM Mobile normalizes it to "precision": 8.

step

Positive number or null.

null

Sets the permitted increment for validation and numeric stepping. When no unit precision applies, a whole-number step displays zero decimal places, and a fractional step displays the number of decimal places in that increment.

Use the following step values for common increments:

1 for whole numbers
0.01 for cents
0.25 for quarter-unit increments

Note:

Starting with version 2026.07.2, replace "step": "any" with a positive numeric increment, such as "step": 0.01, or omit step when no increment is needed. If "any" remains configured, FSM Mobile normalizes it to null, so no increment is applied.

stepper

Boolean.

false

Shows increment/decrement controls. It works with step; it does not change numeric validation by itself.

unit

String identifier or "".

""

Selects a named Number formatting profile from the mobile context's unit collection. A matching profile can set the effective display/input precision and add a prefix or suffix; it does not change the stored number or set min, max, step, stepper, or value. An unrecognised identifier produces unadorned numeric formatting.

Related Topics