reportSales & Receivablesofficial - Microsoftderived - from the source, no model textobsolete - pending

Report 101 "Customer - List"

Base Application · Microsoft.Sales.Reports

Across versionsobsolete pending since 28.0

  1. BC23-27present
  2. BC28declaration changed
  3. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Codeunit 368 "Format Document" (calls)Format DocumentAccounts receivable analytics (Learn pages)Accounts receivable analyticsCustomer List (report) (Learn pages)Customer List (report)

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 · captioned “Customer List” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Customer List
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite
ObsoleteState Pending
ObsoleteTag 28.0
ObsoleteReason This report is obsolete and will be removed in a future version.

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

Deprecations

  • object: Pending 28.0 (#if not CLEAN28), “This report is obsolete and will be removed in a future version.”

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

Evidence 3 sources