Page 7204 "CDS Integration Solutions"
Base Application · Microsoft.Integration.D365Sales
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.D365Sales · captioned “Dataverse Integration Solutions” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | ‘Dataverse Integration Solutions’, Comment = ‘Dataverse is the name of a Microsoft Service and should not be translated.’ |
| SourceTable | CDS Solution |
| 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 | Unique Name | UniqueName | — |
| Friendly Name | FriendlyName | — | |
| Version | Version | — | |
| Installed On | InstalledOn | — | |
| Managed | IsManaged | — |
Triggers
OnAfterGetRecord, OnInit
Relations
- source table Table 5394 “CDS Solution”
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.
- Codeunit 7201 “CDS Integration Impl.” (4 calls:
OnInit → CheckConnectionRequiredFields,OnInit → GetIntegrationSolutions,OnInit → GetTempConnectionName, …)
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 Integration Solutions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.