reportSales & Receivablesofficial - Microsoftderived - from the source, no model text

Report 104 "Customer - Detail Trial Bal."

Base Application · Microsoft.Sales.Reports

Across versions

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

Neighbourhood 4 connected objects and pages

Codeunit 368 "Format Document" (calls)Format DocumentAccounts receivable analytics (Learn pages)Accounts receivable analyticsCustomer - Detail Trial Balance (report) (Learn pages)Customer - Detail Trial Bala…Financial analytics (Learn pages)Financial analytics

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 - Detail Trial Bal.
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Procedures

  • InitializeRequest(ShowAmountInLCY: Boolean; SetPrintOnlyOnePerPage: Boolean; SetExcludeBalanceOnly: Boolean): Initializes the report request options for the Customer Detail Trial Balance report.

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

Evidence 4 sources