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

Report 7150 "Item Dimensions - Detail"

Base Application · Microsoft.Inventory.Reports

Open in Claude7150.mdSource on GitHub

Across versions

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

Neighbourhood 4 connected objects and pages

Codeunit 7151 "ItemAViewEntryToValueEntries" (calls)ItemAViewEntryToValueEntriesInventory analytics (Learn pages)Inventory analyticsInventory and Warehouse Reports and Analytics (Learn pages)Inventory and Warehouse Repo…Item Dimensions - Detail (report) (Learn pages)Item Dimensions - Detail (re…

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 Dimensions - Detail
UsageCategory ReportsAndAnalysis
ApplicationArea Dimensions

Procedures

6 local procedures, no public ones.

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.

Documented on Microsoft Learn

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

Evidence 4 sources