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

Page 5386 "Integration Fields Lookup"

Base Application · Microsoft.Integration.SyncEngine

Across versions

  1. BC23-27not present
  2. BC28added
  3. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 5383 "Integration Field" (relates to)Integration FieldPage 5383 "Man. Int. Field Mapping Wizard" (calls)Man. Int. Field Mapping Wizard

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 · BC28-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible false
SourceTable Integration Field
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
Control2 Table No. Table No. Specifies the number of the table this field belongs to.
Field Name Field Name Specifies the name of the field.
Field Caption Field Caption Specifies the caption of the field, that is, the name that will be shown in the user interface.
Is Runtime IsRuntime Specifies whether the field is a runtime field. Runtime fields are created on the fly and do not exist in the database schema.

Procedures

  • GetSelectedFields(var SelectedIntegrationField: Record "Integration Field")

Relations

Called by

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: "Integration Fields Lookup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources