Page 20402 "Qlty. Inspection Template"

Quality Management · Microsoft.QualityManagement.Configuration.Template · captioned “Quality Inspection Template” · BC29-30 · source at ea08af5e · facts from BC29

Properties

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).

Actions

Procedures

2 local procedures, no public ones.

Triggers

OnAfterGetRecord, OnInsertRecord

Relations

• source table Table 20402 “Qlty. Inspection Template Hdr.”

Pages and codeunits on this table

• Page 20404 “Qlty. Inspection Template List” (card page)

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 20458 “Qlty. Mgmt. Feature Telemetry” (1 call: OnInsertRecord → LogFeatureUptakeSetup)

Recent changes

• 2026-08-20 #10270 [Quality Management] Repair and improve XML documentation of procedures (main, BC30, refactor)

Documented on Microsoft Learn

• Quality management overview
• Create a sampled inspection automatically from production output
• Create an inspection manually from item tracking
• Create an inspection automatically from a warehouse receipt and reinspect the lot
• Create quality inspection templates
• Create scheduled quality inspections
• Quality management setup and configuration
• Set up quality inspection generation rules
• Troubleshoot quality management features

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. Inspection Template"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.