BC Observatoryunofficial, made by waldo
tableextensionInventoryofficial - Microsoftderived - from the source, no model text

Table extension 20403 "Qlty. Entry Summary"

Quality Management · Microsoft.QualityManagement.Integration.Inventory.Tracking

Open in Claude20403.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Table 20405 "Qlty. Inspection Header" (relates to)Qlty. Inspection HeaderTable 338 "Entry Summary" (relates to)Entry Summary

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.Integration.Inventory.Tracking · BC29-30 · source at ea08af5e · facts from BC29

Extends Entry Summary.

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
20400 Qlty. Inspection Count Integer Specifies the count of available quality inspections for the item tracking combination. FlowField: count(“Qlty. Inspection Header” where(“Source Lot No.” = field(“Lot No.”), “Source Serial No.” = field(“Serial No.”), “Source Package No.” = field(“Package No.”))); not editable

Relations

Ask your agent

Procedure bodies are not stored here (D10). 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: "tableextension", object_name: "Qlty. Entry Summary"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources