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

Table 5337 "Temp Integration Field Mapping"

Base Application · Microsoft.Integration.SyncEngine

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Table 5335 "Integration Table Mapping" (relates to)Integration Table Mapping

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

Properties

Property Value
Caption Temp 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 Source Field No. Integer —
4 Destination Field No. Integer —
5 Validate Destination Field Boolean —
6 Bidirectional Boolean —
7 Constant Value Text[100] —
8 Not Null Boolean —

Keys

  • Key1: No. (clustered)

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "Temp Integration Field Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources