pagePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Page 5548 "Contoso Modules Part"

ContosoCoffeeDemoDataset · Microsoft.DemoTool

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 3 connected objects and pages

Table 5161 "Contoso Demo Data Module" (relates to)Contoso Demo Data ModuleCodeunit 5193 "Contoso Demo Tool" (calls)Contoso Demo ToolCodeunit 8703 "Feature Telemetry" (calls)Feature Telemetry

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.

ContosoCoffeeDemoDataset · Microsoft.DemoTool · captioned “Available Modules” · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Available Modules
Extensible false
SourceTable Contoso Demo Data Module
PageType ListPart
UsageCategory Administration
ApplicationArea All

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
General Name Name Specifies the demo data module name
Install Install Specifies the demo data module installation level. It indicates which data was included and can vary between “Setup Data,” meaning that only settings and configurations were installed, or “All,” in which case setup, master data, transactions, and history were installed.

Procedures

  • GetContosoRecord(var ContosoDemoDataModuleTemp: Record "Contoso Demo Data Module" temporary) (internal)
  • SetContosoRecord(var ContosoDemoDataModuleTemp: Record "Contoso Demo Data Module" temporary) (internal)

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

Evidence 1 sources