Codeunit 2584 "Dim Corr Analysis View"
Base Application · Microsoft.Finance.Dimension.Correction
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Finance.Dimension.Correction · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Job Queue Entry |
Events published
OnAfterShouldUpdateAnalysisView(var AnalysisView: Record "Analysis View"; var DimensionCorrection: Record "Dimension Correction"; var Result: Boolean)(integration): Integration event raised after determining whether an analysis view should be updated following dimension correction.OnUpdateSelectedAnalysisViewsOnAfterSetFilter(var AnalysisView: Record "Analysis View")(integration): Integration event raised after applying filters to analysis views for update processing.
Procedures
UpdateAnalysisViews(var DimensionCorrection: Record "Dimension Correction"): Updates analysis views affected by dimension correction operations.
Plus 2 local procedures.
Triggers
OnRun
Relations
- runs on Table 472 “Job Queue Entry”
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 2580 “Dimension Correction Mgt” (1 call:
ShouldUpdateAnalysisView → GetDimCorrectionChanges) - Codeunit 410 “Update Analysis View” (1 call:
UpdateSelectedAnalysisViews → Update)
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: "Dim Corr Analysis View"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.