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

# Attributes

Configure attributes to store and reference connector and processor-level data in Smart Connect.

Attributes in Smart Connect store named values associated with connectors and processors. They enable processors to reference and use data that varies by connector or processor context.

## What is an attribute?

An attribute is a simple key-value pair that:

* Associates a **Name** and **Value** with a specific connector and/or processor
* Allows processors to retrieve data dynamically based on context
* Enables reusable configuration across multiple processors

Attributes are stored in the **NANAttributeTable** and queried by processor/connector ID and attribute name.

## Attribute structure

| Field       | Description                                                                                          | Required |
| ----------- | ---------------------------------------------------------------------------------------------------- | -------- |
| Name        | Attribute identifier                                                                                 | Yes      |
| Value       | Stored value                                                                                         | Yes      |
| ConnecterId | Connector this attribute is associated with                                                          | Yes      |
| ProcessorId | Processor this attribute applies to (optional; empty = applies to all processors for this connector) | No       |

## Creating and managing attributes

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

### Basic workflow

1. **Set the connector:** Choose which connector this attribute applies to
2. **Set the processor (optional):** Leave empty for connector-level attributes, or specify a processor for processor-specific attributes
3. **Enter the attribute name:** Use a clear, descriptive identifier (e.g., `DefaultVendor`, `FileFormat`, `ProcessingMode`)
4. **Enter the value:** The actual value the processor will retrieve

### Attribute retrieval in code

Processors can retrieve attribute values using:

```
NANAttributeTable::getAttributeValue(_processorId, _connectorId, _attributeName)
```

This function:

1. First looks for a processor-specific attribute (matching both processor and connector)
2. If not found, looks for a connector-level attribute (processor ID empty)
3. Returns the value if found, or null if not found

## Use cases

* **Connector configuration:** Store connection-specific settings (API endpoint overrides, file paths, format options)
* **Processor parameters:** Store processor-specific behavior flags or values
* **Dynamic routing:** Use attribute values to influence data routing decisions

## Best practices

* **Use consistent naming:** Create a naming convention (e.g., `Connector_Setting`, `Processor_Flag`)
* **Document the purpose:** Use descriptive names so team members understand what each attribute controls
* **Start with connector-level:** Define attributes at the connector level first; override with processor-specific values only when needed
* **Version settings:** If an attribute value changes behavior, test in a non-production environment first

## Related pages

* [Connectors and connectivity](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/connectors-and-connectivity.md)
* [Processors and transformations](https://docs.dynalogic.com/birds-smart-connect/readme/processors-and-transformations.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/attributes.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.
