Page 5361 "Integration Field Mapping List"
Base Application · Microsoft.Integration.SyncEngine
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.SyncEngine · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Integration Field Mapping List |
| SourceTable | Integration Field Mapping |
| PageType | List |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | Status | Status | Specifies if field synchronization is enabled or disabled. from the table field |
| Field No. | Field No. | Specifies the number of the field in Business Central. from the table field | |
| Field Name | NAVFieldName |
Specifies the name of the field in Business Central. | |
| Integration Table Field No. | Integration Table Field No. | Specifies the field number of the integration field to map to the Business Central field. | |
| Integration Field Name | CRMFieldName |
Specifies the name of the integration field to map to the Business Central field. | |
| Direction | Direction | Specifies the direction of the synchronization. from the table field | |
| Constant Value | Constant Value | Specifies the constant value that the mapped field will be set to. from the table field | |
| Transformation Rule | Transformation Rule | Specifies a rule for transforming imported text to a supported value before it can be mapped to a specified field in Microsoft Dynamics 365. from the table field | |
| Transformation Direction | Transformation Direction | Specifies the direction of the transformation. from the table field | |
| Validate Field | Validate Field | Specifies if the field should be validated during assignment in Business Central. | |
| Validate Integration Table Fld | Validate Integration Table Fld | Specifies if the integration field should be validated during assignment in Dynamics 365 Sales. from the table field | |
| Clear Value on Failed Sync | Clear Value on Failed Sync | Specifies if the field value should be cleared in case of integration error during assignment in Dynamics 365 Sales. from the table field | |
| Not Null | Not Null | Specifies if the data transfer should be skipped for destination fields whose new value is going to be null. This is only applicable for GUID fields, such as OwnerId, that must not be changed to null during synchronization. from the table field | |
| User Defined | User Defined | Specifies if the field is generated manually through the integration table mapping wizard. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Reset Transformation Rules | Resets the transformation rules for the integration table mapping. | |
| New Field Mapping | Create a new integration field mapping. |
Procedures
2 local procedures, no public ones.
Triggers
OnAfterGetRecord
Relations
- source table Table 5336 “Integration Field Mapping”
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 10 “Type Helper” (1 call:
GetFieldCaption → GetField)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "page", object_name: "Integration Field Mapping List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.