pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 5383 "Man. Int. Field Mapping Wizard"

Base Application · Microsoft.Integration.SyncEngine

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-27unchanged
  4. BC281 procedures added
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 5384 "Man. Int. Field Mapping" (relates to)Man. Int. Field MappingPage 5386 "Integration Fields Lookup" (calls)Integration Fields Lookup

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 · captioned “User Defined Field Mappings” · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption User Defined Field Mappings
SourceTable Man. Int. Field Mapping
PageType ListPart
ApplicationArea All

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
repeaterName Field Name Table Field Caption Specifies the name of the field in Business Central. from the table field
Integration Field Name Int. Table Field Caption Specifies the name of the integration field to map to the Business Central field. from the table field
Direction Direction Specifies the synchronization direction. from the table field
ConstValue Const 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
ValidateField Validate Field Specifies if the field should be validated during assignment. from the table field
ValidateIntegrTableField Validate Integr. Table Field Specifies if the field should be validated during assignment in the integration table. from the table field

Procedures

  • SetValues(lIntegrationMappingTableId: Integer; lIntegrationMappingIntTableId: Integer; lIntegrationMappingName: Code[20]) (internal)
  • GetValues(var ManIntFieldMapping: Record "Man. Int. Field Mapping" temporary) (internal)
  • LookupIntegrationField(var IntegrationField: Record "Integration Field"): Boolean + BC28

Relations

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: "page", object_name: "Man. Int. Field Mapping Wizard"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources