> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/component-basics/inserting-dynamic-text/how-to-format-dates-and-numbers.md).

# How to Format Dates and Numbers

* If the [Magic Text](/component-basics/inserting-dynamic-text.md) you add is for a Number or Date Property, you can customize how that information is formatted.
* **To see formatting options, click on the pencil in the Magic Text chip**
*  For numbers:
  * Saving Numbers in the Database
    * Whole numbers must be entered without symbols (no commas or periods). Decimals must be denoted by either a period (.) or a comma (,)
  * Formatting Number for Displaying
    * You can select whether the number should have commas, be abbreviated, or be displayed as currency. 
  * Prefixes and Suffixes
    * Prefixes and Suffixes can make your text even more magical by smartly showing the right word depending on whether the number is singular or plural.
    * For example, if you are showing a count of Trips, you can set the singular suffix to "Trip" and the plural suffix and "Trips."  Then your app will automatically show "1 Trip"  or "2 Trips"
* For dates:
  * You can elect whether you want your data formatted as a Date or Date/Time, Day of the Week, or Relative (i.e., 3 days ago)

![](https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LhGHkPsv15svPIU5I7C%2F-MRvDP-kJ2Il_oc1tJ1p%2F-MRvE74X9HMkD41tojl4%2FTrip%20Example%20\(1\).gif?alt=media\&token=da4a80dd-5580-4df5-8e47-65b81695453d)


---

# 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://help.adalo.com/component-basics/inserting-dynamic-text/how-to-format-dates-and-numbers.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.