> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/placeholders.md).

# Placeholders

Configure placeholder values for reuse across Smart Connect connectors and processors.

Placeholders in Smart Connect are predefined values that can be referenced and reused across connectors and processors. They provide a central location to define configuration values.

## What is a placeholder?

A placeholder is a named, reusable value that:

* Stores a configuration value centrally (e.g., a GL account, vendor code, file path)
* Can be referenced by multiple processors and connectors
* Simplifies maintenance by allowing updates in one location

Placeholders are stored in the **NANPlaceholderTable** with just a name and description.

## Placeholder structure

| Field         | Description                           | Required |
| ------------- | ------------------------------------- | -------- |
| PlaceholderId | Unique name for the placeholder       | Yes      |
| Description   | Purpose and usage of this placeholder | No       |

## Creating a placeholder

Navigate to **Smart Connect > Setup > Placeholders** or search for "NANPlaceholderTable" in the F\&O search.

### Basic workflow

1. **Enter the placeholder ID:** Use a clear, descriptive identifier (e.g., `DefaultGLAccount`, `VendorApprovalThreshold`, `FileInputPath`)
2. **Enter the description:** Explain what this placeholder is used for and which processors reference it
3. **Save**

### Placeholder naming conventions

Create a consistent naming pattern to organize placeholders by category:

**Examples:**

* `GL_DefaultAccount` – GL account values
* `Vendor_ApprovalLimit` – Vendor configuration
* `File_InputPath` – File system paths
* `Process_Timeout` – Timeout settings

## Using placeholders

Processors reference placeholder values in code or configuration. The placeholder name is used to retrieve the associated value at runtime.

**Example:**

* Processor needs to use a default GL account
* References placeholder: `DefaultGLAccount`
* Looks up the value from the placeholder table
* Uses that value during processing

## Best practices

* **Use descriptive IDs:** Make the purpose obvious from the name alone
* **Document thoroughly:** Add detailed descriptions explaining when and why each placeholder is used
* **Organize by prefix:** Group related placeholders with consistent naming (GL\_, Vendor\_, File\_, etc.)
* **Version settings:** If a placeholder value changes behavior, test the change in a non-production environment first
* **Regular reviews:** Periodically check which placeholders are actually used; remove unused ones
* **Access control:** Restrict placeholder editing to authorized personnel through F\&O security roles

## Troubleshooting

| Issue                               | Cause                                                         | Solution                                                                                         |
| ----------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Placeholder value not found         | Placeholder ID misspelled or doesn't exist                    | Verify exact spelling of placeholder ID; confirm it exists in the table                          |
| Multiple processors using old value | Placeholder changed but some processors still use old version | Update all processors that reference this placeholder simultaneously or create a new placeholder |
| Placeholder not accessible          | Incorrect access permissions                                  | Verify your user role has permission to view/edit placeholder table                              |

## Related pages

* [Attributes](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/attributes.md)
* [Processors and transformations](https://docs.dynalogic.com/birds-smart-connect/readme/processors-and-transformations.md)
* [Connectors and connectivity](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/connectors-and-connectivity.md)


---

# 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.dynalogic.com/birds-smart-connect/setup-and-configuration/placeholders.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.
