BC Observatoryunofficial, made by waldo
tableIntegration & APIsofficial - Microsoftderived - from the source, no model text

Table 5336 "Integration Field Mapping"

Base Application · Microsoft.Integration.SyncEngine

Open in Claude5336.mdSource on GitHub

Across versions

  1. BC23present
  2. BC241 fields added, 1 procedures added
  3. BC25declaration changed
  4. BC26-27unchanged
  5. BC2815 fields changed
  6. BC29-30unchanged

Neighbourhood 9 connected objects and pages

Table 1237 "Transformation Rule" (relates to)Transformation RuleTable 5335 "Integration Table Mapping" (relates to)Integration Table MappingPage 5361 "Integration Field Mapping List" (pages and codeunits on it)Integration Field Mapping ListPage 5363 "Match Based Coupling Criteria" (pages and codeunits on it)Match Based Coupling CriteriaPage 7236 "Master Data Synch. Fields" (pages and codeunits on it)Master Data Synch. FieldsTable extension 7234 "MasterDataMgtFieldMapping" (extended by)MasterDataMgtFieldMappingCodeunit 10 "Type Helper" (calls)Type HelperManage master data synchronization (Learn pages)Manage master data synchroni…Set up companies to synchronize master data (Learn pages)Set up companies to synchron…

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

Base Application · Microsoft.Integration.SyncEngine · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 7236 “Master Data Synch. Fields” (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” (“Integration Table Mapping”.Name)
3 Field No. Δ BC28 Integer Specifies the number of the field in Business Central.
4 Integration Table Field No. Δ BC28 Integer Specifies the number of the field in Dynamics 365 Sales.
6 Direction Δ BC28 Option Specifies the direction of the synchronization. OptionCaption: Bidirectional,ToIntegrationTable,FromIntegrationTable
7 Constant Value Δ BC28 Text[100] Specifies the constant value that the mapped field will be set to.
8 Validate Field Δ BC28 Boolean Specifies if the field should be validated during assignment in Business Central.
9 Validate Integration Table Fld Δ BC28 Boolean Specifies if the integration field should be validated during assignment in Dynamics 365 Sales.
10 Clear Value on Failed Sync Δ BC28 Boolean Specifies if the field value should be cleared in case of integration error during assignment in Dynamics 365 Sales.
11 Status Δ BC28 Option Specifies if field synchronization is enabled or disabled. OptionCaption: Enabled,Disabled
12 Not Null Δ BC28 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 Δ BC28 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” (Transformation Rule); DataClassification SystemMetadata
14 Transformation Direction Δ BC28 Enum “CDS Transformation Direction” Specifies the direction of the transformation. enum Enum 5397 “CDS Transformation Direction”
15 Use For Match-Based Coupling Δ BC28 Boolean Specifies whether to match on this field when looking for the entity to couple to.
16 Case-Sensitive Matching Δ BC28 Boolean Specifies whether the matching on this field should be case-sensitive.
17 Match Priority Δ BC28 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. via Page 7236 “Master Data Synch. Fields”
19 Integration Field Caption Text[250] —
20 User Defined + BC24 Δ BC28 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) + BC24 − BC24
  • CreateRecord(IntegrationTableMappingName: Code[20]; TableFieldNo: Integer; IntegrationTableFieldNo: Integer; SynchDirection: Option; ConstValue: Text; ValidateField: Boolean; ValidateIntegrationTableField: Boolean; Enabled: Boolean; TransformationRule: Code[20]; UserDefined: Boolean) + BC24 − BC24 (internal)
  • SetMatchBasedCouplingFilters(IntegrationTableMapping: Record "Integration Table Mapping") (internal)

Plus 2 local procedures.

Triggers

OnInsert, OnModify

Relations

Pages and codeunits on this table

Extended by

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.

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.

Evidence 1 sources