reportFinanceofficial - Microsoftderived - from the source, no model text

Report 37 "Balance Comp. - Prev. Year"

Base Application · Microsoft.Finance.GeneralLedger.Reports

Across versions

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

Neighbourhood 3 connected objects and pages

Codeunit 9200 "Matrix Management" (calls)Matrix ManagementBalance Comp. - Prev. Year (report) (Learn pages)Balance Comp. - Prev. Year (…Built-in finance reports in Business Central (Learn pages)Built-in finance reports in …

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

Properties

Property Value
Caption Balance Comp. - Prev. Year
UsageCategory ReportsAndAnalysis
ApplicationArea Basic, Suite

Procedures

  • SetEndingDate(): Calculates ending date for the period based on the starting date and accounting periods. Uses the next accounting period’s starting date minus one day as the ending date.
  • SetPreviousDates(): Calculates corresponding previous year dates by subtracting one year from current period dates. Sets both starting and ending dates for previous year comparison and validates fiscal year alignment.
  • RoundAmount(Value: Decimal): Text[30]: Formats decimal amounts according to the specified rounding factor for report display. Utilizes Matrix Management codeunit for consistent amount formatting across reports.
  • InitializeRequest(NewPeriodStartingDate: Date; NewPeriodEndingDate: Date; NewPreviousStartingDate: Date; NewPreviousEndingDate: Date; NewRoundingFactor: Option; NewIndent: Option): Initializes report parameters for programmatic execution with date ranges and formatting options. Sets period dates, previous year comparison dates, rounding factors, and indentation levels for automated report generation.

Plus 2 local procedures.

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: "Balance Comp. - Prev. Year"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 3 sources