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.