---
id: object/table/5336
type: object
title: Table 5336 "Integration Field Mapping"
summary: Table 5336 "Integration Field Mapping" in Base Application (Microsoft.Integration.SyncEngine). 19 fields, 3 public procedures. Present since at least BC23, still in BC30, changed in BC24-25, BC28.
tier: official
language: en
tags:
  - table
  - base application
versions:
  introduced: null
  last_changed: "28"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 4b64ceeae4a2f7217967efd937a11282218f9bce08794706e2e5bac67943f46a
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Integration/SynchEngine/IntegrationFieldMapping.Table.al
    title: src/Layers/W1/BaseApp/Integration/SynchEngine/IntegrationFieldMapping.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/admin-set-up-data-sync
    - https://learn.microsoft.com/dynamics365/business-central/admin-sync-master-data
  objects: []
  features: []
  topics:
    - topic/business-central/development-and-administration/synchronize-master-data-across-companies
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: table
object_id: 5336
name: Integration Field Mapping
namespace: Microsoft.Integration.SyncEngine
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
  - "25"
  - "28"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 19
  procedures: 5
  events: 0
  subscribers: 0
relations:
  out: 2
  referenced_by: 0
  pages: 3
  extended_by: 1
  event_subscribers: 0
  calls: 1
  called_by: 0
  implements: 0
---

# Table 5336 "Integration Field Mapping"

> Table 5336 "Integration Field Mapping" in Base Application (Microsoft.Integration.SyncEngine). 19 fields, 3 public procedures. Present since at least BC23, still in BC30, changed in BC24-25, BC28.

Base Application · Microsoft.Integration.SyncEngine · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Integration/SynchEngine/IntegrationFieldMapping.Table.al) · facts from BC29

Learn documents this table through its pages: [Page 7236 "Master Data Synch. Fields"](../page/7236.md) (2 Learn pages).

## Properties

| Property | Value |
|---|---|
| Caption | Integration Field Mapping |
| DataClassification | CustomerContent |

## Fields

Explanation: the field's ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | No. | Integer | — | AutoIncrement |
| 2 | Integration Table Mapping Name | Code[20] | — | TableRelation [Table 5335 "Integration Table Mapping"](../table/5335.md) ("Integration Table Mapping".Name) |
| 3 | Field No. | Integer | Specifies the number of the field in Business Central. |  |
| 4 | Integration Table Field No. | Integer | Specifies the number of the field in Dynamics 365 Sales. |  |
| 6 | Direction | Option | Specifies the direction of the synchronization. | OptionCaption: Bidirectional,ToIntegrationTable,FromIntegrationTable |
| 7 | Constant Value | Text[100] | Specifies the constant value that the mapped field will be set to. |  |
| 8 | Validate Field | Boolean | Specifies if the field should be validated during assignment in Business Central. |  |
| 9 | Validate Integration Table Fld | Boolean | Specifies if the integration field should be validated during assignment in Dynamics 365 Sales. |  |
| 10 | Clear Value on Failed Sync | Boolean | Specifies if the field value should be cleared in case of integration error during assignment in Dynamics 365 Sales. |  |
| 11 | Status | Option | Specifies if field synchronization is enabled or disabled. | OptionCaption: Enabled,Disabled |
| 12 | Not Null | Boolean | 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. |  |
| 13 | Transformation Rule | Code[20] | Specifies a rule for transforming imported text to a supported value before it can be mapped to a specified field in Microsoft Dynamics 365. | TableRelation [Table 1237 "Transformation Rule"](../table/1237.md) (Transformation Rule); DataClassification SystemMetadata |
| 14 | Transformation Direction | Enum "CDS Transformation Direction" | Specifies the direction of the transformation. | enum [Enum 5397 "CDS Transformation Direction"](../enum/5397.md) |
| 15 | Use For Match-Based Coupling | Boolean | Specifies whether to match on this field when looking for the entity to couple to. |  |
| 16 | Case-Sensitive Matching | Boolean | Specifies whether the matching on this field should be case-sensitive. |  |
| 17 | Match Priority | Integer | Specifies in which priority order will the groups of matching fields be used to find a match. |  |
| 18 | Field Caption | Text[250] | Specifies the caption of the field. <small>via [Page 7236 "Master Data Synch. Fields"](../page/7236.md)</small> |  |
| 19 | Integration Field Caption | Text[250] | — |  |
| 20 | User Defined | Boolean | Specifies if the field is generated manually through the integration table mapping wizard. |  |

## Keys

- Key1: No. (clustered)
- Key2: Integration Table Mapping Name
- Key3: Match Priority
- Key4: Transformation Rule

## Procedures

- `CreateRecord(IntegrationTableMappingName: Code[20]; TableFieldNo: Integer; IntegrationTableFieldNo: Integer; SynchDirection: Option; ConstValue: Text; ValidateField: Boolean; ValidateIntegrationTableField: Boolean)`
- `CreateRecord(IntegrationTableMappingName: Code[20]; TableFieldNo: Integer; IntegrationTableFieldNo: Integer; SynchDirection: Option; ConstValue: Text; ValidateField: Boolean; ValidateIntegrationTableField: Boolean; Enabled: Boolean; TransformationRule: Code[20]; UserDefined: Boolean)` (internal)
- `SetMatchBasedCouplingFilters(IntegrationTableMapping: Record "Integration Table Mapping")` (internal)

Plus 2 local procedures.

## Triggers

OnInsert, OnModify

## Relations

- Transformation Rule: TableRelation [Table 1237 "Transformation Rule"](../table/1237.md)
- Integration Table Mapping Name: TableRelation [Table 5335 "Integration Table Mapping"](../table/5335.md)

## Pages and codeunits on this table

- [Page 5361 "Integration Field Mapping List"](../page/5361.md) (source table)
- [Page 5363 "Match Based Coupling Criteria"](../page/5363.md) (source table)
- [Page 7236 "Master Data Synch. Fields"](../page/7236.md) (source table)

## Extended by

- [Table extension 7234 "MasterDataMgtFieldMapping"](../tableextension/7234.md)

## 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"](../codeunit/10.md) (1 call: `IsGUIDField → GetField`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC24-25, BC28

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## 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: "table", object_name: "Integration Field Mapping")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.