Table 8363 "Dimension Perspective Name"
Base Application · Microsoft.Finance.FinancialReports
Across versions
- BC23-27not present
- BC28added
- BC29-30unchanged
Neighbourhood 8 connected objects and pages
Base Application · Microsoft.Finance.FinancialReports · BC28-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 8364 “Dimension Perspectives” (1 Learn page).
Properties
| Property | Value |
|---|---|
| Caption | Dimension Perspective Name |
| DataClassification | CustomerContent |
| LookupPageId | Dimension Perspectives |
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 | Name | Code[10] | — | NotBlank |
| 2 | Description | Text[100] | Specifies the description of the dimension perspective. The description is not shown on the final report but is used to provide more context when using the definition. | |
| 3 | Internal Description | Text[250] | Specifies the internal description of the dimension perspective. The internal description is not shown on the final report but is used to provide more context when using the definition. | |
| 4 | Perspective Type | Enum “Dimension Perspective Type” | Specifies how the financial report dimension perspectives will be totaled by. If you select Custom, then you can set up a combination of fields to total by on a dimension-by-dimension basis. Otherwise, perspectives are automatically created and totaled by each dimension value or business unit. | enum Enum 8363 “Dimension Perspective Type” |
| 5 | Analysis View Name | Code[10] | Specifies the name of the analysis view you want the dimension perspective to use. This field is optional. | TableRelation Table 363 “Analysis View” (Analysis View) |
Keys
- PK: Name (clustered)
Trigger event subscribers
- OnAfterValidateEvent(Perspective Type): Codeunit 8365 “DimPerspectiveCustom” AfterValidatePerspectiveType
Procedures
LookupPerspectiveType(var PerspectiveTypeText: Text): BooleanPerspectiveTypeToText(PerspectiveType: Enum "Dimension Perspective Type"): TextTextToPerspectiveType(Text: Text): Enum "Dimension Perspective Type"
Plus 3 local procedures.
Triggers
OnDelete
Relations
- lookup page Page 8364 “Dimension Perspectives”
- Analysis View Name: TableRelation Table 363 “Analysis View”
Referenced by
3 fields in 3 objects relate to this table (TableRelation or CalcFormula).
- Table 8364 “Dimension Perspective Line”: Name
- Table 88 “Financial Report”: DimPerspective
- Table 89 “Financial Report User Filters”: FinReportDimPerspectiveName
Pages and codeunits on this table
- Page 8364 “Dimension Perspectives” (source table)
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 27 “Confirm Management” (1 call:
ValidateAnalysisViewName → GetResponseOrDefault)
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: "Dimension Perspective Name"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.