Number

Number fields store one numeric value. They can control range, precision, integer-only rules, display prefix or suffix, and validation messages.

Use a number field when users need to enter values such as amount, quantity, rate, score, duration, or any value used by numeric filtering and analytics.

Basic Settings

Setting	Description
Name	The field label shown to users. It is required and should describe the business meaning of the value clearly
API Name	The stable technical name used by data APIs, scripts, formulas, imports, and integrations. It is required
Required	Requires users to enter a value before the record can be saved
Readonly	Shows the value but prevents users from editing it
Disabled	Makes the field unavailable for normal use
Hidden	Stores the value while hiding it from normal form pages

Number Field Config

Setting	Description
Placeholder	Prompt text shown before users enter a number
Min	Lowest value users can submit
Max	Highest value users can submit
Step	Increment used by the number input control
Precision	Decimal places kept for the number. Leave it empty when precision should be automatic
Prefix	Text shown before the number, such as a currency symbol
Suffix	Text shown after the number, such as a unit or percent sign
Min Message	Custom message shown when the value is lower than the minimum
Max Message	Custom message shown when the value is higher than the maximum
Multiple Of	Requires the value to be a multiple of the configured number
Multiple Of Message	Custom message shown when the multiple rule fails
Integer Message	Custom message shown when integer-only validation fails
Validate Trigger	Controls when validation runs: when the value changes, when the field loses focus, or when the record is submitted
Input Status	Adds a visual status to the input, such as warning or error
Integer Only	Allows only integer values
Controls	Shows plus and minus controls in the number input
Field Color	Sets the display color used for the field
Help Text	Helper copy shown near the field. Use it to explain units, range, or precision rules

Common Examples

Scenario	Suggested Config
Amount	Prefix $, precision 2, min 0
Quantity	Integer only enabled, min 0, step 1
Percentage	Suffix %, min 0, max 100, precision 2
Rating	Min 1, max 5, step 1

Configuration Tips

Tip	Description
Set min and max together	Range limits make validation clearer and avoid unexpected values
Use suffix for units	A suffix such as kg, hours, or % tells users what the number means
Use precision for money and rates	Fixed precision keeps displayed values consistent
Enable integer-only for counts	Counts, quantities, and sequence-like values usually should not accept decimals