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

Page 5332 "SDK Version List"

Base Application · Microsoft.Integration.Dataverse

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 9160 "TempStack" (relates to)TempStackCodeunit 5330 "CRM Integration Management" (calls)CRM Integration ManagementCodeunit 7201 "CDS Integration Impl." (calls)CDS Integration Impl.

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

Properties

Property Value
Caption SDK Version List
SourceTable TempStack
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
Group SDK Version StackOrder Specifies the version of the Microsoft Dynamics 365 (CRM) software development kit that is used for the connection.

Triggers

OnOpenPage

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.

Called by

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: "SDK Version List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources