Data Mapping - Mapping Data to Databean Paths of UI Components
Databean path is a storage for holding the data of any UI Widget or an UI Component.
DataBean Path stores the data required by the UI components. Combine the Data Bean Path and Field to:
Render the data inside a UI component such as Grid, Map, Gauge, Input box, and so on.
Pass the data to server-side components (such as JavaScript, DB Actions, and third-party API).
Retrieve and bind the data from various data sources such as DBMS and external applications.
Although the DataBean Path can be configured for any UI component, it is usually configured for parent UI components (such as Section, Map, Grid, and Chart).
Child elements such as radio button, checkbox, label, text box, grid column, chart series, consume the data stored in the DataBean Path of their parent component.
Depending on whether the UI component supports a repeating data set (Grid, Chart) or a simple data set (Section), DataBean Path stores the data as a JSON Array or a JSON Object respectively.
DataBean Path is created when the page is loaded or when the data loader is executed.
The DataBean Path is used by client-side scripts for event handling, binding data, controlling the visibility of the UI component, and calculating values dynamically.
For more information, see Autoload and Data Loader Examples
Each UI component on the screen can have its own DataBean Path. All such DataBean Paths are assigned to a root variable data.
For example, if a screen has one Section and one Grid, each having its own DataBean Path, then the Section's Data Bean Path is accessed as data.<section's data bean path> and the Grid's DataBean Path is accessed as data.<grid's data bean path>.