> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/setting-up/additional-config/subscriptions-table-columns/custom-attribute-columns.md).

# Custom Attribute Columns

#### **LFS version:** custom attributes require v14.14 or later. Current Payment Method requires v14.22 or later.

The **Limio - Subscriptions Table Config** tab adds two column types to the subscriptions table, on top of the standard columns described in [Column Config Tool](/salesforce/setting-up/additional-config/subscriptions-table-columns/customise-subscriptions-table.md).

## Custom attribute columns

A custom attribute column shows a subscription attribute from Limio, for example a customer reference number.

1. Open the **Limio - Subscriptions Table Config** tab.
2. Click **Add Attribute**. The **Add Custom Attribute** window opens.
3. Enter the **Attribute Display Name**, which is the column heading the agent sees.
4. Enter the **Attribute Field Name**, which is the attribute key exactly as Limio returns it, for example `CRN`.
5. Click **Save**. The attribute joins the list of available columns on the left.
6. Select the attribute in that list so it moves to the chosen columns on the right.
7. Save the configuration.

The tool holds a separate configuration for Business Accounts and for Person Accounts. Add the attribute on both tabs when both kinds of customer need it.

If the column is empty, check that the field name matches the attribute key in Limio exactly, including capital letters.

{% hint style="info" %}
A custom attribute column is not a Salesforce field, so field-level security does not apply to it. Every agent who can open the subscriptions table sees the value.
{% endhint %}

## Current Payment Method column

Current Payment Method is a standard column. Select it from the available columns on the left, in the same way as any other column. It is not added through **Add Attribute**.

The column shows the payment method of the subscription. Under Zuora it shows:

| Payment method | What the agent sees                              |
| -------------- | ------------------------------------------------ |
| Card           | The card brand and the last four digits          |
| Direct debit   | `Direct Debit` and the last four digits          |
| PayPal         | `PayPal` and the customer's PayPal email address |
| Bank transfer  | The transfer type and the last four digits       |
| Google Pay     | `Google Pay`                                     |

Under Stripe, the column shows card details only.

The column is not sortable.

{% hint style="info" %}
The column loads its value for each row separately, so a long table takes longer to load. Add the column only where agents need it.
{% endhint %}

## Moving the configuration between orgs

The column configuration is stored as **Limio - Config** records, not as metadata. A change set does not move it. Set up the columns again in the target org, or move the records with a data tool.


---

# 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.limio.com/salesforce/setting-up/additional-config/subscriptions-table-columns/custom-attribute-columns.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.