> 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/substitute-text.md).

# Substitute Text

## Description

The Substitute Text part allows you to search for one or more instances of text or numeric strings and prepend, append, or replace it with alternative strings.

**Node Type:** This part is available in process nodes in the *Text manipulation* dropdown menu.

**Used With:** This part can be used in all LogicNets frameworks-based applications as well as in applications that do not use a framework.

## Use

You can use this part for data conversion and for removing illegal characters in data fields. Illegal characters are usually introduced from external systems.

## Editor Fields

| Field Name       | Description/Use                                                                                                                               | Type/Options           | Mandatory/Optional |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ------------------ |
| Input text path  | This is the name of the object where the text string is stored.                                                                               | Data Object\*          | Mandatory          |
| Output text path | This is the name of the object where the converted text string is stored.                                                                     | Data Object\*          | Mandatory          |
| find             | This is the string to find and apply rules to.                                                                                                | Alphanumeric Character | Mandatory          |
| replace          | This is the string that replaces the 'find' contents.                                                                                         | Alphanumeric Character | Optional           |
| preppend         | This is the string the system adds to the front of the 'find' contents.                                                                       | Alphanumeric Character | Optional           |
| append           | This is the string the system adds after the 'find' contents.                                                                                 | Alphanumeric Character | Optional           |
| number of times  | This is the number of times the system should perform instruction on the contents of the 'find' cell, starting from position 1 of the string. | Number                 | Optional           |

\* This input field is expecting a data object; do not use $(...) around the object name.

## Example

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6c3e2e6466d6024b3ed79e4b4fddfd3e4d76db5c%2Fff761d3b-f7f0-4078-bb3b-a009fd5f8f35.jpg?alt=media)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ce713cc74b9fa6ef14a23437b1de66a47b1823f4%2F735e23bf-0562-42bd-9bbf-80001bd1ef29.png?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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/substitute-text.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.