codeunitInventoryofficial - Microsoftderived - from the source, no model text

Codeunit 20422 "Qlty. Demo Data Mgmt."

Quality Management · Microsoft.QualityManagement.Setup

Across versions

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

Neighbourhood 3 connected objects and pages

Codeunit 2504 "Extension Management" (calls, 2 links)Extension ManagementCodeunit 20457 "Qlty. Demo Data Runner" (calls)Qlty. Demo Data RunnerPage 20422 "Qlty. Demo Data Launcher" (calls)Qlty. Demo Data Launcher

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.

Quality Management · Microsoft.QualityManagement.Setup · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Procedures

  • InstallOrOpenDemoData(): Installs the QM demo data app if not installed, otherwise opens the Contoso Demo Tool.
  • LaunchDemoData(): Launches the Contoso Demo Tool if installed, otherwise shows installation message.
  • IsContosoDemoToolInstalled(): Boolean: Checks if the Quality Management Contoso Coffee Demo Dataset app is installed.

Plus 2 local procedures.

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.

Called by

Recent changes

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: "codeunit", object_name: "Qlty. Demo Data Mgmt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources