Report 28 "Dimensions - Detail"
Base Application · Microsoft.Finance.Dimension
Across versions
- BC23-28present
- BC29declaration changed
- BC30unchanged
Neighbourhood 4 connected objects and pages
Base Application · Microsoft.Finance.Dimension · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dimensions - Detail |
| UsageCategory | ReportsAndAnalysis |
| ApplicationArea | Dimensions |
Events published
OnAfterGetRecordAnalysisViewOnBeforeSetEntryFilterGroup(var AnalysisViewEntry: Record "Analysis View Entry"; AnalysisView: Record "Analysis View")(integration): Integration event raised after analysis view record processing and before setting entry filter groups. Enables custom filtering and processing of analysis view entries during report generation.OnPrintDetailOnAfterTempGLEntrySetFilters(var TempGLEntry: Record "G/L Entry" temporary)(integration): Integration event raised after setting filters on temporary G/L entries during detail printing. Enables custom filter modification for detailed G/L entry reporting.OnPreReportOnAfterDimValSetFilters(var DimensionValue: Record "Dimension Value")(integration): Integration event raised after setting filters on dimension values during report preprocessing. Enables custom dimension value filtering for report data preparation.
Procedures
6 local procedures, no public ones.
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.
- Codeunit 413 “AnalysisViewEntryToGLEntries” (1 call:
PrintDetail → GetGLEntries)
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: "Dimensions - Detail"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.