> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/common-for-several-products/smart-dimensions/text-note-settings.md).

# Text Note Settings

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FKDLgf6UA0Ib3ZdZoocUU%2F0.jpeg?alt=media)

**Text Note Type** - select Text Type which should be used for Notes.

**Offset** – offset Text Note in horizontal direction, away from dimension line.

**Text Note Position** – vertical alignment – in the center of the dimension line, or above it.

**Create Text Notes** – defines if you want to create them.

{% hint style="info" %}
Offset, Position and Create Text Notes settings are not visible if you go to Smart Dimensions configurations through Dimensioning Rules of Smart Assemblies because they are overwritten by Smart Assemblies settings in the Note Positioning tab when Assembly is created.
{% endhint %}

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FW5z2L6YjlKtDiAH3KO47%2F1.jpeg?alt=media)

**Dimension Text formula**

Here you can define what information you want to see in a text note. Use Add, Remove buttons, Available Parameters, Prefix, Suffix options, and arrows to re-order them.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FbzLPqtKQemGw9nU9eHBi%2F2.jpeg?alt=media)

**Text Note** – text defined in each tab of dimensioning, for example 'On Front Faces'.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FSbiY5uNE332KJxwzswpb%2F3.jpeg?alt=media)

**Text Note Parameter** – also selected in each dimensioning tab, but here you can select different parameters from the element.

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FJSRtPy1Wmfzdl5WlhvDy%2F4.jpeg?alt=media)

**Quantity** – it gives the number of elements:

![](https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FzMx8m2tReGNBtisOgyVK%2F5.jpeg?alt=media)


---

# 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.besmart.software/common-for-several-products/smart-dimensions/text-note-settings.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.