Data binding is exactly what the name implies, joining data from an existing or created table to a given UX component. Data can also be bound to a control as, for example, when detail view containing textbox controls is bound to list control that is in turn bound to a SQL table on a server. You can visit the main Data Binding page for more information and guides on how to implement data binding. The properties in this section are for UX components that have already been data-bound.
- Compute data binding code at design time
Generally, when a UX component is bound to tables, the data binding code is computed at run-time. In large UX components this can slow down the initial load of the UX component. Therefore, you might prefer to compute the data binding code at design-time. However, if you choose this option, saving the UX component in the UX component Builder after you make an edit, this will take slightly longer.
- Prompt before computing data binding code
Display a confirmation prompt before computing the data binding code. If your UX is bound to a complex data structure, computing the data binding code can be relatively time consuming. If you have made minor edits to the UX that do not affect any of the data binding, you will not need to recompute the data binding code each time you save the UX in the builder. The prompt is displayed below.
- Automatically refresh schema of tables when component is opened for editing
If checked, when the component is opened for editing, the Data Binding schema is automatically refreshed for each table.
- Prompt before refreshing schema
Display a confirmation prompt before refreshing the schema. The prompt is shown below. This property is displayed when the 'Automatically refresh schema of tables when component is opened for editing' property is checked. You can opt for the 'NoPrompt' option, in which case the component will open without a refresh prompt being displayed.