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

Page 7207 "CDS Environments"

Base Application · Microsoft.Integration.Dataverse

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Table 7202 "CDS Environment" (relates to)CDS EnvironmentTable 7202 "CDS Environment" (pages and codeunits on it)CDS EnvironmentCodeunit 7203 "CDS Environment" (calls)CDS Environment

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 · captioned “Dataverse User Environments” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption ‘Dataverse User Environments’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’
Extensible false
SourceTable CDS Environment
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 Environment Name ‘Specifies the name of the Dataverse environment.’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’
Linked Linked ‘Specifies whether the Dataverse environment is the linked environment.’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’
URL Url ‘Specifies the URL of the Dataverse environment.’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’

Relations

Pages and codeunits on this table

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

Evidence 1 sources