tableFinanceofficial - Microsoftderived - from the source, no model text

Table 363 "Analysis View"

Base Application · Microsoft.Finance.Analysis

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-28unchanged
  4. BC2916 fields changed
  5. BC30unchanged

Neighbourhood 26 connected objects and pages

Table 348 "Dimension" (relates to, 4 links)DimensionTable 15 "G/L Account" (relates to)Table 220 "Business Unit" (relates to)Business UnitTable 841 "Cash Flow Account" (relates to)Cash Flow AccountPage 556 "Analysis View List" (pages and codeunits on it, 2 links)Analysis View ListCodeunit 410 "Update Analysis View" (pages and codeunits on it)Update Analysis ViewPage 555 "Analysis View Card" (pages and codeunits on it)Analysis View CardTable extension 2625 "StatAccAnalysisView" (extended by)StatAccAnalysisViewCodeunit 2621 "Stat. Acc. Analysis View Mgt." (event subscribers, 3 links)Stat. Acc. Analysis View Mgt.Codeunit 6239 "Sust. Acc. Analysis View Mgt." (event subscribers, 2 links)Sust. Acc. Analysis View Mgt.Codeunit 410 "Update Analysis View" (calls, 3 links)Update Analysis ViewCodeunit 27 "Confirm Management" (calls, 2 links)Page 554 "Analysis by Dimensions" (calls)Analysis by DimensionsTable 333 "Column Layout Name" (referenced by)Table 361 "Analysis by Dim. Parameters" (referenced by)Analysis by Dim. ParametersTable 364 "Analysis View Filter" (referenced by)Analysis View FilterTable 365 "Analysis View Entry" (referenced by)Analysis View EntryTable 366 "Analysis View Budget Entry" (referenced by)Table 369 "Selected Dimension" (referenced by)Table 376 "G/L Account (Analysis View)" (referenced by)Table 6225 "Sust. Account (Analysis View)" (referenced by)Table 727 "Analysis by Dim. User Param." (referenced by)Table 8363 "Dimension Perspective Name" (referenced by)Table 84 "Acc. Schedule Name" (referenced by)Analyze data by dimensions (Learn pages)Create analysis reports (Learn pages)

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

Learn documents this table through its pages: Page 555 “Analysis View Card” (2 Learn pages), Page 556 “Analysis View List” (2).

Properties

Property Value
Caption Analysis View
DataClassification CustomerContent
Permissions TableData “Analysis View Entry” = rimd, TableData “Analysis View Budget Entry” = rimd

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No. Name Type Explanation Notes
1 Code Δ BC29 Code[10] Specifies the code for this entry. NotBlank
2 Name Δ BC29 Text[50] Specifies the name.
3 Account Source Δ BC29 Enum “Analysis Account Source” Specifies an account that you can use as a filter to define what is displayed in the Analysis by Dimensions window. enum Enum 7133 “Analysis Account Source”
4 Last Entry No. Δ BC29 Integer Specifies the number of the last general ledger entry you posted, prior to updating the analysis view.
5 Last Budget Entry No. Δ BC29 Integer Specifies the number of the last item budget entry you entered prior to updating the analysis view.
6 Last Date Updated Δ BC29 Date Specifies the date on which the analysis view was last updated.
7 Update on Posting Δ BC29 Boolean Specifies if the analysis view is updated every time that you post a general ledger entry. not editable
8 Blocked Δ BC29 Boolean Specifies that the related record is blocked from being posted in transactions, for example a customer that is declared insolvent or an item that is placed in quarantine.
9 Account Filter Δ BC29 Code[250] Specifies which accounts are shown in the analysis view. TableRelation Table 15 “G/L Account”, Table 841 “Cash Flow Account” (if (“Account Source” = const(“G/L Account”)) “G/L Account” else if (“Account Source” = const(“Cash Flow Account”)) “Cash Flow Account”)
10 Business Unit Filter Code[250] — TableRelation Table 220 “Business Unit” (Business Unit)
11 Starting Date Δ BC29 Date Specifies the starting date of the campaign analysis.
12 Date Compression Δ BC29 Option Specifies the period that the program will combine entries for, in order to create a single entry for that time period. OptionCaption: None,Day,Week,Month,Quarter,Year,Period
13 Dimension 1 Code Δ BC29 Code[20] Specifies one of the four dimensions that you can include in an analysis view. TableRelation Table 348 “Dimension”
14 Dimension 2 Code Δ BC29 Code[20] Specifies one of the four dimensions that you can include in an analysis view. TableRelation Table 348 “Dimension”
15 Dimension 3 Code Δ BC29 Code[20] Specifies one of the four dimensions that you can include in an analysis view. TableRelation Table 348 “Dimension”
16 Dimension 4 Code Δ BC29 Code[20] Specifies one of the four dimensions that you can include in an analysis view. TableRelation Table 348 “Dimension”
17 Include Budgets Δ BC29 Boolean Specifies whether to include an update of analysis view budget entries, when updating an analysis view.
18 Refresh When Unblocked Boolean —
19 Reset Needed Boolean Data update needed caption

Keys

  • Key1: Code (clustered)
  • Key2: Account Source

Events published

  • OnAfterAnalysisViewReset(var AnalysisView: Record "Analysis View") (integration): Integration event raised after analysis view reset operations are completed.
  • OnAfterCopyAnalysisViewFilters(var AnalysisView: Record "Analysis View"; ObjectType: Integer; ObjectID: Integer; AnalysisViewCode: Code[10]; var GLAcc: Record "G/L Account") (integration): Integration event raised after copying analysis view filters to selected dimensions.
  • OnBeforeValidateDimension1Code(var Rec: Record "Analysis View"; var xRec: Record "Analysis View") (integration): Integration event raised before validating Dimension 1 Code field changes.
  • OnBeforeValidateDimension2Code(var Rec: Record "Analysis View"; var xRec: Record "Analysis View") (integration): Integration event raised before validating Dimension 2 Code field changes.
  • OnBeforeValidateDimension3Code(var Rec: Record "Analysis View"; var xRec: Record "Analysis View") (integration): Integration event raised before validating Dimension 3 Code field changes.
  • OnBeforeValidateDimension4Code(var Rec: Record "Analysis View"; var xRec: Record "Analysis View") (integration): Integration event raised before validating Dimension 4 Code field changes.
  • OnBeforeValidateDateCompression(var Rec: Record "Analysis View"; var xRec: Record "Analysis View"; var IsHandled: Boolean) (integration): Integration event raised before validating Date Compression field changes.
  • OnBeforeValidateBlocked(var Rec: Record "Analysis View"; var xRec: Record "Analysis View"; var IsHandled: Boolean) (integration): Integration event raised before validating the Blocked field on Analysis View records. Enables custom validation logic and the ability to bypass standard validation.
  • OnBeforeValidateStartingDate(var Rec: Record "Analysis View"; var xRec: Record "Analysis View"; var IsHandled: Boolean) (integration): Integration event raised before validating the Starting Date field on Analysis View records. Enables custom validation logic and the ability to bypass standard validation.
  • OnBeforeValidateIncludeBudgets(var Rec: Record "Analysis View"; var xRec: Record "Analysis View"; var IsHandled: Boolean) (integration): Integration event raised before validating the Include Budgets field on Analysis View records. Enables custom validation logic and the ability to bypass standard validation.
  • OnBeforeValidateAccountFilter(var Rec: Record "Analysis View"; var xRec: Record "Analysis View"; var IsHandled: Boolean) (integration): Integration event raised before validating the Account Filter field on Analysis View records. Enables custom validation logic and the ability to bypass standard validation.
  • OnBeforeValidateBusinessUnitFilter(var Rec: Record "Analysis View"; var xRec: Record "Analysis View"; var IsHandled: Boolean) (integration): Integration event raised before validating the Business Unit Filter field on Analysis View records. Enables custom validation logic and the ability to bypass standard validation.
  • OnBeforeCheckIfLastEntryOrDateIsSet(var Rec: Record "Analysis View"; var Result: Boolean; var IsHandled: Boolean) (integration): Integration event raised before checking if Last Entry or Date field is set on Analysis View records. Enables custom logic for determining analysis view update requirements.
  • OnBeforeSetUpdateOnPosting(var Rec: Record "Analysis View"; NewUpdateOnPosting: Boolean) (integration): Integration event raised before setting the Update on Posting field on Analysis View records. Enables custom logic for managing automatic analysis view updates.
  • OnValidateAccountFilter(var AnalysisView: Record "Analysis View"; var xRecAnalysisView: Record "Analysis View") (integration): Integration event raised when validating account filter on Analysis View records. Enables additional validation or processing during account filter validation.
  • OnLookupAccountFilter(var Handled: Boolean; var AccountFilter: Text; var AnalysisView: Record "Analysis View") (integration): Integration event raised when performing account filter lookup on Analysis View records. Enables custom lookup behavior for account filter field.
  • OnGetAnalysisViewSupported(var AnalysisView: Record "Analysis View"; var IsSupported: Boolean) (integration): Integration event for determining if an Analysis View is supported by custom implementations. Enables extensibility for additional analysis view types beyond standard G/L and Cash Flow.

Procedures

  • AnalysisViewReset(): Resets the analysis view by clearing all analysis view entries and resetting tracking fields.
  • CheckDimensionIsTracked(DimensionCode: Code[20]): Boolean: Checks if a specified dimension code is tracked by any of the four dimension code fields in the analysis view.
  • CheckDimensionsAreRetained(ObjectType: Integer; ObjectID: Integer; OnlyIfIncludeBudgets: Boolean): Validates that required dimensions are retained for specified objects in analysis views.
  • CheckViewsAreUpdated(): Checks if all analysis views are updated with the latest transaction data and prompts for update if needed.
  • UpdateAllAnalysisViews(ShowWindow: Boolean): Updates all analysis views in the system, optionally showing a progress window.
  • UpdateLastEntryNo(): Updates the last entry number for all non-blocked analysis views to the latest G/L entry number.
  • ValidateDelete(FieldName: Text): Validates that the user confirms deletion of analysis view data when modifying configuration fields.
  • AnalysisViewBudgetReset(): Resets the analysis view budget entries by deleting all budget entries and resetting the last budget entry number.
  • ValidateModify(FieldName: Text): Validates that the user confirms modification of analysis view data when changing configuration fields.
  • CopyAnalysisViewFilters(ObjectType: Integer; ObjectID: Integer; AnalysisViewCode: Code[10]): Copies analysis view dimension filters to selected dimensions for a specified object.
  • CheckIfLastEntryOrDateIsSet(): Boolean: Checks if the analysis view has been configured with last entry tracking or last date updated.
  • SetUpdateOnPosting(NewUpdateOnPosting: Boolean): Sets the Update on Posting field for all analysis views to the specified value.
  • SetSkipConfirmationDialogue(): Sets a flag to skip confirmation dialogues during analysis view operations.
  • RunAnalysisByDimensionPage(): Opens the Analysis by Dimensions page for the current analysis view.
  • ShowResetNeededNotification(): Shows a notification to the user indicating that the analysis view needs to be reset.

Plus 6 local procedures.

Triggers

OnDelete

Relations

Referenced by

11 fields in 11 objects relate to this table (TableRelation or CalcFormula).

Pages and codeunits on this table

Extended by

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

Evidence 1 sources