BC Observatoryunofficial, made by waldo
reportPurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Report 329 "Vendor - Trial Balance"

Base Application · Microsoft.Purchases.Reports

Open in Claude329.mdSource on GitHub

Across versions

  1. BC23-27present
  2. BC282 procedures added, 1 procedures removed
  3. BC29declaration changed
  4. BC30unchanged

Neighbourhood 3 connected objects and pages

Accounts payables analytics (Learn pages)Accounts payables analyticsFinancial analytics (Learn pages)Financial analyticsVendor - Trial Balance (report) (Learn pages)Vendor - Trial Balance (repo…

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.Purchases.Reports · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Vendor - Trial Balance
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Procedures

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

Evidence 4 sources