BC Observatoryunofficial, made by waldo
reportSales & Receivablesofficial - Microsoftderived - from the source, no model text

Report 211 "Customer - Payment Receipt"

Base Application · Microsoft.Sales.Reports

Open in Claude211.mdSource on GitHub

Across versions

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

Neighbourhood 2 connected objects and pages

Accounts receivable analytics (Learn pages)Accounts receivable analyticsCustomer - Payment Receipt (report) (Learn pages)Customer - Payment Receipt (…

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

Properties

Property Value
Caption Customer - Payment Receipt

Procedures

1 local procedures, no public ones.

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: "Customer - Payment Receipt"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources