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

Report 714 "Inventory - Vendor Purchases"

Base Application · Microsoft.Inventory.Reports

Open in Claude714.mdSource on GitHub

Across versions

  1. BC23-27present
  2. BC281 procedures added
  3. BC29declaration changed
  4. BC30unchanged

Neighbourhood 4 connected objects and pages

Analytics in purchasing (Learn pages)Analytics in purchasingInventory analytics (Learn pages)Inventory analyticsInventory Vendor Purchases (report) (Learn pages)Inventory Vendor Purchases (…Purchasing reports and analytical tasks (Learn pages)Purchasing reports and analy…

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 Inventory - Vendor Purchases
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Procedures

3 local procedures, no public ones.

Triggers

OnPreReport

Recent changes

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). 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: "Inventory - Vendor Purchases"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 5 sources