---
schema_version: "1"
id: 74e958e345ba3ca318d16ab3e100eb8deacf27a4c5e14ade4b6072aab29905b4
title: Bind Components to Data
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/mobile_ama_bind_components.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.mobile_ama_bind_components.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8ae7e1889a38044c1459c8aa8daa06b73e1d6c9e95b01a8614dc0a22709a1db0
description: Connect your app's components to live Salesforce data in two phases. First add a data source to a screen, then bind components to the fields in that source.
release: "264"
---
# Bind Components to Data

Connect your app's components to live Salesforce data in two phases. First add a data source to a screen, then bind components to the fields in that source.

Data binding has two phases. First you bring data into the Mobile App Designer by adding a data source to a screen. Then you bind individual components on that screen to the fields in the source. A component shows live data only after its screen has a data source.

## How Data Binding Works

Data binding works at the screen level. Each screen has its own data icon in the data tab that shows which data sources are attached to that screen, such as an account, an opportunity, or a custom object. Click the icon to see which components on the screen are bound to each source.

A data source defines the records available on a screen, including the object, filters, sort order, and how many records to retrieve. After the source is on the screen, you bind components to its fields with the expression builder. You can also describe a binding in plain language in the agent panel.

## Single and Dynamic Components

When a single component, such as a text component, is bound to a source that returns more than one record, the component shows the field from the first record. To repeat content across every record in a source, use a dynamic component, such as a list, row, or carousel.

## Data Visibility

Bound components respect the field-level access of the logged-in user. Users see only the fields their access level allows. For example, a Salesforce admin can see all fields, while a customer or partner user sees only the fields available to them.

- **[Add a Data Source to a Screen](https://help.salesforce.com/s/articleView?id=xcloud.mobile_ama_add_data_source.htm&release=264.0.0&type=5)**  
    Define the records you want available on a screen, including the object, filters, sort order, and how many records to retrieve.
- **[Bind a Component to a Field](https://help.salesforce.com/s/articleView?id=xcloud.mobile_ama_bind_component_to_field.htm&release=264.0.0&type=5)**  
    Connect a single component, such as a text component, to a field from a data source so that it shows one field value.
- **[Bind a Dynamic Component to Repeat Across Records](https://help.salesforce.com/s/articleView?id=xcloud.mobile_ama_bind_dynamic_component.htm&release=264.0.0&type=5)**  
    Use a dynamic component, such as a list, row, or carousel, to repeat its content across every record in a data source instead of showing only the first record.