> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/example-gallery/example-projects-for-parts/dbgrid3-number-formatting.md).

# dbgrid3 Example Project - Number Formatting

This example project shows the *dbgrid3* part with custom formatting of number columns that override the default number formatting available in the *System Configuration* package Localization tab - see [this](/release-9/platform-documentation/system-administration/system-settings/system-configuration-localization-tab.md) article.

Download the project and import it into your Designer. Run the project in TEST mode and examine the dbgrid column settings in the CODE view.

Note that these configurations are not yet part of the public Designer Editor. These will become available in a future release but currently they require a special license to access. Please contact your LogicNets Account Manager and ask about the Advanced Designer License that provides access to the CODE view.

## Attachments

* [DB Grid Example Number Formatting.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/18pt8p-DB-Grid-Example-Number-Formatting.zip)


---

# 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://community-test.logicnets.com/release-9/example-gallery/example-projects-for-parts/dbgrid3-number-formatting.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.