The data mapping record screen configures a single inbound mapping from an ERP system to the platform and opens when you select an existing record from Data mappings.
Screen structure
Area | Purpose |
General Info | Contains the mapping identity fields and its metadata section. |
Response Preview | Displays a preview of the raw ERP response for the mapping. |
Logic Rules | Holds the transformation or conditional logic applied to the mapping. |
Relation | Provides access to the Property Mapping view, which lists the field-level mappings that make up the record. |
Api Preview | Shows how the mapped data appears in the platform API response. |
General Info fields
Field | Description |
Name | Forms part of the mapping identity. |
Erp model | Identifies the ERP model root associated with the mapping. |
Api model | Identifies the platform API model associated with the mapping. |
Categories | Identifies a categories mapping. |
Category | Identifies a category mapping. |
Basic Query | The associated basic query opens its record when selected. |
User QUery | This field is read-only. |
Metadata | Carries additional metadata for the record. |
Property mapping view
The Property Mapping view renders the Data Mapping Lines table and is reached through the Relation tab. Each row represents one field mapping between the ERP response and the platform API model.
Column | Description |
Api Name | Names the field as it appears in the platform API model. |
Response Name | Names the field as it appears in the ERP response payload. |
Match | Indicates whether the API name and response name are resolved as a match. |
Erp logic rule | Identifies the logic rule applied on the ERP side for the field. |
Data mapping logic rule | Identifies the logic rule applied at the data mapping level for the field. |
Table controls
Control | Description |
Rows per page | Sets the number of rows displayed on each page. |
Pagination | Provides previous and next page buttons and specific page numbers for navigating between pages. |
Notes
A persistent alert appears when the record is locked because it is used by an API endpoint, and Save is disabled in that state.
Related