Page 5194 "Contoso Demo Tool"
ContosoCoffeeDemoDataset · Microsoft.DemoTool
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 6 connected objects and pages
ContosoCoffeeDemoDataset · Microsoft.DemoTool · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Contoso Demo Tool |
| Extensible | false |
| SourceTable | Contoso Demo Data Module |
| PageType | List |
| 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 |
| Data Level | Data Level | 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. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Generate | Generate | Generate demo data for selected module | |
| Generate Setup Data | Generate setup data for selected modules | ||
| Processing | Configure | Open the configuration page for the selected module |
Triggers
OnOpenPage
Relations
- source table Table 5161 “Contoso Demo Data Module”
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 5193 “Contoso Demo Tool” (2 calls:
OnOpenPage → FilterModulesWithApplicationAreas,OnOpenPage → RefreshModules) - Codeunit 8703 “Feature Telemetry” (1 call:
OnOpenPage → LogUptake)
Documented on Microsoft Learn
- Introduction to Contoso Coffee Demo Data
- Set up Contoso Coffee demo data for quality management
- Contoso demo data
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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 Demo Tool"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.