Skip to main content
A Number field stores numerical data. Picking the right number type matters: it controls how much storage the field uses, what range of values it can hold, and whether decimal precision is exact or approximate.

​
Number types

For monetary values, always use Numeric / Decimal. Floats and doubles are approximate and accumulate rounding errors. A 0.1 + 0.2 = 0.30000000000000004 mistake in a financial column is a real problem.

​
Configuration options

Number field type configuration

​
How it appears in the API

Integer types are exposed as Int in GraphQL. Float, Double Precision, and Numeric are exposed as Float (or a custom Decimal scalar where exactness matters). See the GraphQL API Explorer for the generated schema.

​
Permissions

Number fields obey the per-role read and write rules configured in Role-Based Access.

​
FAQ

Numeric / Decimal. It stores exact values with a configurable precision and scale. Floats and doubles are inexact and will produce rounding errors over time.
For most app data, Integer is more than enough (about ±2.1 billion). Reach for Big Integer only when you genuinely expect very large counts or are storing identifiers that exceed Integer’s range.
Both are approximate. Float has about 6 digits of precision; Double Precision has about 15. Use Double when you need more precision; Float when storage size matters and 6 digits is enough.
Yes. Existing values are auto-converted where the new type can hold them. Narrowing the type — for example, from Integer to Small Integer — will fail if any value is out of range.