Page 20422 "Qlty. Demo Data Launcher"
Quality Management · Microsoft.QualityManagement.Setup
Across versionsobsolete pending since 29.0
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
Quality Management · Microsoft.QualityManagement.Setup · captioned “Quality Management Demo Data” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Quality Management Demo Data |
| PageType | Card |
| UsageCategory | None |
| ApplicationArea | All |
| ObsoleteState | Pending |
| ObsoleteTag | 29.0 |
| ObsoleteReason | Unused. Use the “Install Demo Data” action on the Quality Management Setup page instead. |
Triggers
OnInit
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 20422 “Qlty. Demo Data Mgmt.” (1 call:
OnInit → LaunchDemoData)
Deprecations
- object: Pending 29.0 (#if not CLEAN29), “Unused. Use the “Install Demo Data” action on the Quality Management Setup page instead.”
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: "Qlty. Demo Data Launcher"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.