This section explains how to map individual form fields and grid-based records to their corresponding data table fields, depending on whether the data is captured as a single value or as multiple records. Field Mapping can be configured using either Single Elements or Multiple Elements.
Used to map individual application fields directly to Data Table fields.
Example
- Application Field → Employee Name
- Data Table Column → Employee Name
Used when mapping grid/sub-form data.
Example
- Expense Grid → Expense Data Table.
- Each row in the grid becomes a separate record in the table.
Conditions in App Data Functions act as logical rules that define:
They allow you to apply decision-based logic before data is saved into a data table. By default, the App Data Function executes unconditionally. To execute the Data Function only when specific criteria are met, click Add Conditions and configure the required conditions.
Conditions are configured:
They act as a control gate between: Application → Data Function → Data Table
All employee records must be stored in a Master Employee Table. Additionally, department-wise records must also be stored separately. Conditions Applied:
| Condition | Action |
|---|---|
| Department = Product | Store the record in the Product Employee Table |
| Department = Marketing | Store the record in the Marketing Employee Table |