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

Report 6520 "Item Tracing Specification"

Base Application · Microsoft.Inventory.Reports

Open in Claude6520.mdSource on GitHub

Across versions

  1. BC23-28present
  2. BC29declaration changed
  3. BC30unchanged

Neighbourhood 2 connected objects and pages

Codeunit 10 "Type Helper" (calls)Type HelperCodeunit 9806 "Field Selection" (calls)Field Selection

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.

Base Application · Microsoft.Inventory.Reports · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Item Tracing Specification

Procedures

  • TransferEntries(var ItemTrackingEntry: Record "Item Tracing Buffer")

Plus 2 local procedures.

Triggers

OnPreReport

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.

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: "report", object_name: "Item Tracing Specification"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources