Field Mappings

Documentation home

See also:         

Understanding Ebase Integration

Working with Forms

The field mappings dialog shown below allows you to maintain the mappings between the form fields and the resource fields for all resources contained in the business view associated with the form. When an FPL script command or API method is executed to read or write data to or from a resource e.g. fetch, update, sendmail etc, the system will automatically transfer data between the form fields and the resource fields for all mapped fields.

Note that if you use the import fields from external resource button on the fields toolbar, the field mappings are created automatically by the system.

The Primary form field mappings tab displays form field mappings via the form’s business view.

The Component form field mappings tab displays field mappings for deployed components that have a component business view. Component mappings are read only. When this tab is selected, an additional dropdown of deployed components is displayed at the top of the panel.

Select the resource to be mapped from the dropdown list at the top of the dialog. The table display will contain one line for each field within that resource.

Resource field: the name of the resource field

Mapped to form field: the name of the form field to which this resource field is mapped. Click on the name to display a dropdown list of all fields within the form. Select 'None' to indicate that there is no mapping.

Resource field description: the description of the field - copied from the resource definition.

The Auto-map button can be used to automatically create mappings for like-named form fields/resource fields. In the example above, all resource fields and form fields have the same name and the mappings could be generated using the auto-map feature.

The auto-map feature will only create a mapping if there isn't one already for that resource field.

The Auto-map prefix can be used with the auto-map button to create mappings to form fields and table columns with a given prefix. For example, entering a prefix such as C1_ will create mappings to form fields C1_ADDRESS, C1_AREA_CODE, etc, from resource fields ADDRESS, AREA_CODE, etc.

However, if the selected resource is assigned to a table on the form, then the Auto-map prefix is ignored and the form's table prefix is automatically used instead.  If this resource contains both table(s) and field(s) the auto-map button will only map the fields for the first table prefix it finds.  Non-table fields will not be mapped.

The Remove all mappings for resource button removes all mappings for the resource currently selected. The Mapped to form field values are replaced with None.