> ## 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 dynamic values

> Use HubSpot fields, associated records, form answers, card info, and external data without code.

# Data and dynamic values

A fixed value is the same on every record. A dynamic value is pulled from the card's context when the card is shown. Dynamic values let you build one card that adapts to each record and user.

## Where can dynamic values be used?

You will find the field picker in texts, headings, statuses, stat tiles, default values, visibility rules, and many actions. In a text field, fixed text and multiple dynamic fields can be combined into a single sentence.

Example:

> \[Record · Company name] has \[Associated deals · Count] active relationships.

In value fields, you pick either a **Fixed value** or a single field from the catalog.

## Data sources in the field picker

### The current HubSpot record

Choose **Record · \[field name]** to use a field from the record the card is on. When HubSpot is connected, the portal's real labels and fields are used. Otherwise, well-known demo/standard fields are shown.

If a field does not appear in the search results, choose **Advanced: add by internal name** and enter the HubSpot field's internal name. The field is added to the card's data needs automatically.

### Associated records

You can choose:

* **Associated \[object] · Count**;
* **Associated \[object] · Sum of \[field]**;
* **Associated \[object] · Rows** for a table, chart, or repeater.

When you pick an association, Card Studio creates the required data source automatically. You do not have to configure a separate data tab first.

"Sum of" only produces a meaningful value for numeric fields. If you pick a text field, the runtime cannot produce a usable total.

### External systems

Once a system has been added under **Connected systems**, its fields and lists appear in the field pickers. Labels and formats can be changed centrally for the card. See [Connected systems](/building/connected-systems).

### Form

Each input field provides a value under **Form · \[the field's label]**. Use it in texts, rules, or actions, for example to write an answer back to HubSpot.

### Selected associated record

If a dropdown, multiple choice, or button group field pulls its options from associated records, the fields on the selected row become available as **Selected \[object] · \[field]**.

This lets the user pick a contact first, and then show that contact's email or update a property on exactly that contact.

### Steps

On a card with a flow, you can use the current step, the current step number, and the number of steps. Use them in text or visibility rules, for example.

### Card info

Card info contains the record ID, object type, portal ID, user ID, and user name. Use these values with care; a technical ID is rarely suitable as visible text, but it can be useful in actions or links.

### Row in a repeater

Inside a **Repeater**, the child blocks get the **Row** field group. It refers to the current row, not the whole list. See [Repeater](/components/repeater).

## Automatic data management

Card Studio automatically keeps record and association sources in sync with the fields the card actually uses:

* the record source keeps the fields it needs;
* an association is created when it is selected;
* unused associations and fields can be cleaned up automatically;
* connected systems are not removed automatically, because an unused connection may be intentional.

This also means you should remove or replace a binding before expecting the underlying association to disappear.

## Formatting

External fields can be marked as text, number, currency, date, date and time, percent, or status chip. Table columns also get automatic formats based on field names, e.g. date for `date` and currency for `amount`/`total`.

The authoring locale can be Danish or English. It controls formatting hints on the card; raw CRM values are not changed.

## Common issues

* If a dynamic value is empty, check that the field has a value on the current record.
* If an association shows 0, check that records are actually associated in HubSpot.
* If a field shows its internal name, Card Studio is missing a label from the portal or the field mapping.
* If a "Selected record" value is missing, the input field must use options from an association data source.
* Row fields can only be used inside a repeater.