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.

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.

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.

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.

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.

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.