> 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/platform-documentation/process-node-parts/get-text-length.md).

# Get Text Length

## Description

The *Get Text Length* part allows you to retrieve the number of characters for a given text string.

**Node Type:** This part is located in process nodes under the *Text manipulation* dropdown menu. Note that that in LogicNets versions before 7.3, the part label is *stringfind*.

**Used With:** This part can be used with all frameworks and non-framework-based applications.

## Use

This part is useful in applications that need to work with text strings. For instance, using get text length for code ABC123-X can be the input to the **split text** part to retrieve the last character of the string, letter X.

It can also be used to identify within the logicnet whether a field will overrun the space provided, such that the Designer User can model a different presentation of the string (useful in cases where CSS declarations for text spacing, breaking and overflow are not sufficient).

## Editor Fields

| Field Name  | Description/Use                                                                                          | Type/Options        | Optional/\*\*\*\*Mandatory |
| ----------- | -------------------------------------------------------------------------------------------------------- | ------------------- | -------------------------- |
| Input value | This is the name of the data object containing the source string. Use *$()* around the data object name. | Data Object         | Mandatory                  |
| Output path | This is where you specify the variable to hold the length of the input string.                           | Text \| Data Object | Mandatory                  |


---

# 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/platform-documentation/process-node-parts/get-text-length.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.