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

Page 5372 "CDS Available Virtual Tables"

Base Application · Microsoft.Integration.D365Sales

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 5372 "CDS Av. Virtual Table Buffer" (relates to)CDS Av. Virtual Table BufferCodeunit 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.D365Sales · captioned “Available Virtual Tables - Dataverse” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Available Virtual Tables - Dataverse
Extensible false
SourceTable CDS Av. Virtual Table Buffer
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 Name Phsyical Name Specifies the physical name of the virtual table. from the table field
Display Name Display Name Specifies the display name of the virtual table. from the table field
API Route API Route Specifies the API route of the virtual table. from the table field
Visible Visible Specifies the visibility of the virtual table. from the table field
In Process In Process Specifies whether the enabling of virtual table is in process. from the table field

Actions

Group Action ToolTip Runs
Processing Enable Enables the selected virtual tables in Dataverse environment.
Refresh Refreshes the list of available virtual tables from Dataverse environment.
Open in Dataverse Manage available virtual tables in your Dataverse environment.

Procedures

1 local procedures, no public ones.

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.

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: "CDS Available Virtual Tables"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources