> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hubspotcards.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data and display errors

> Diagnose empty fields, wrong labels, missing lists, connector errors, and unexpected formatting.

# Data and display errors

## A record field is empty

1. Check the value on the specific HubSpot record.
2. Check that the card's object is correct.
3. Select the field again in Card Studio.
4. If the field is custom, search by label or add it by internal name.
5. Check the app scope and the user's field access.

Preview may use sample data. A value in preview therefore does not prove that every live record has the field filled in.

## A field shows a technical name

Card Studio does not have a known label for it. For a connector, use **Rename fields**. For HubSpot, check the portal connection or add the field via the right portal metadata.

## The count or sum of associated records is wrong

* Check the actual HubSpot associations.
* Check that you selected the right object type.
* Only use sum on numeric properties.
* Remember that permissions can hide records from the current user/app.

## A table, chart, or repeater has no list

Select **Data source (list)** again. Available lists come from associated standard objects and the list output of connected systems.

A regular record property is a scalar and cannot be used as a list, even if its text contains separators.

## A connector value is missing

1. Open **Connected systems** and check that the operation has been added.
2. Check the operation's required input data.
3. If the environment uses live data, check the credentials and connection status.
4. Use **Reload data** after a write if cached data is stale.
5. Do not remove and re-add the source as a first fix; it can leave invalid bindings behind.

## Currency, date, or percent looks wrong

Open the connector's **Rename fields** and choose the right format. Table columns also guess from technical field names; pay special attention to fields without `date`, `amount`, or `total` in the name.

Record properties can arrive as machine-format strings. If a value needs to be numeric for a chart or a comparison, the source must deliver a compatible value.

## Dynamic options show the wrong labels

Open the input field and check the primary and secondary label fields. For association options, the properties selected from the source are used. If a needed field is missing, select it in a relevant binding or recreate the options source with the right properties.

## Saved form answers do not come back

* Check that **Save form data on the record** is turned on.
* Check that the card ID, portal, object type, and record ID are the same.
* Wait until the value has been saved before closing the page.
* Remember that a CRM property and Card Studio's form storage are two different layers.