> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/data-types/number.md).

# Number

### Description

A **Number** field is used to store numeric values. The value can be positive or negative and may contain a fractional component (decimals). Number fields can be used in calculations and in mathematical functions within the platform.

When numeric values are displayed on a page, the formatting (such as the thousand-grouping character and decimal separator) is determined by the language settings of the project.

The numeric input field allows numbers of up to **18 digits** (for example: `123456789012345678`). When more digits are entered, the system will display the validation message **`“This is not a valid number.”`**

However, it is important to understand that numeric values follow the **IEEE 754 floating-point standard**, which is also used in many widely used technologies such as **Microsoft Excel and .NET**. Due to this standard, numeric values are stored with a precision of approximately 15 significant digits.

This means that numbers containing more than **15 significant digits cannot always be represented exactly** as numeric values. In such cases, rounding or precision loss may occur during calculations, storage, or data mapping.

If an application needs to store or process numbers with more than **15 digits of precision** (for example identifiers, long reference numbers, or financial identifiers), these values should be stored and handled as **text/string fields instead of numeric fields**.

For additional background and examples, see the related forum discussion:\
[**Large Numbers can be presented in unexpected form**](https://forum.wem.io/link?threadid=808)

### Formatting

The formatting of numbers can be controlled using format strings. Some examples for formatting `1054.32179` are shown below.

```
0000               /* 1054 */
#,000.000          /* 1,054.322 */
000,000,000.00###  /* 000,000,001,054.32179 */
```

### Unknown

An unknown value can be written as `UnknownNumber`.

### Examples

```
1
0
3.14
-1
-0.0054825
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.wem.io/platform/wemreference/data-types/number.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
