BC Observatoryunofficial, made by waldo
codeunitFinanceofficial - Microsoftderived - from the source, no model text

Codeunit 424 "Export Analysis View"

Base Application · Microsoft.Finance.Analysis

Open in Claude424.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 419 "File Management" (calls)File Management

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

Events published

  • OnAfterExportData(var varTempExcelBuffer: Record "Excel Buffer" temporary; var AnalysisViewEntry: Record "Analysis View Entry") (integration): Integration event raised after completing analysis view data export to Excel buffer. Enables custom post-processing of Excel data before file generation and download.
  • OnCreateAnalysisViewEntryPartOnBeforeStartNewRow(var TempExcelBuffer: Record "Excel Buffer" temporary; var AnalysisViewEntry: Record "Analysis View Entry"; AnalysisByDimParameters: Record "Analysis by Dim. Parameters") (integration): Integration event raised before starting a new row when creating analysis view entry data part. Enables custom row formatting and data manipulation during Excel export generation.
  • OnCreateRowWithColumnsCaptionsOnBeforeStartNewRow(var TempExcelBuffer: Record "Excel Buffer" temporary; var AnalysisViewEntry: Record "Analysis View Entry") (integration): Integration event raised before starting a new row when creating column captions. Enables custom header formatting and caption manipulation during Excel export generation.
  • OnExportDataOnAfterCloseBook(var TempExcelBuffer: Record "Excel Buffer" temporary; var AnalysisViewEntry: Record "Analysis View Entry"; AnalysisByDimParameters: Record "Analysis by Dim. Parameters") (integration): Integration event raised after closing the Excel workbook during data export. Enables final workbook customization and post-processing before file completion.
  • OnBeforeCheckCombination(GLAccountSource: Boolean; Show: Integer; AmountField: Integer; var IsHandled: Boolean) (integration): Integration event raised before checking combination validity for export settings. Enables custom validation logic for analysis view export parameter combinations.
  • OnBeforeCreateAnalysisViewEntryPart(var AnalysisViewEntry: Record "Analysis View Entry"; AnalysisView: Record "Analysis View"; var StartDate: Date; var EndDate: Date; AnalysisByDimParameters: Record "Analysis by Dim. Parameters"; var IsHandled: Boolean) (integration): Integration event raised before creating analysis view entry part during export generation. Enables custom date filtering and entry selection logic for analysis view export processing.

Procedures

  • ExportData(var AnalysisViewEntry: Record "Analysis View Entry"; AnalysisByDimParameters: Record "Analysis by Dim. Parameters"): Exports analysis view entry data to Excel format with dimensional breakdown and hierarchical structure. Creates comprehensive Excel report with configurable dimensions and account groupings.
  • GetServerFileName(): Text: Retrieves the server file name for the exported analysis view file. Returns the full server path and filename of the generated Excel export file.
  • SetSkipDownload(): Configures the export process to skip automatic file download after generation. Sets the process to generate the Excel file without triggering browser download dialog.

Plus 26 local procedures.

Triggers

OnRun

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.

Countries that replace it

ES

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: "codeunit", object_name: "Export Analysis View"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources