pageFinanceofficial - Microsoftderived - from the source, no model text

Page 564 "Dimension Selection-Level"

Base Application · Microsoft.Finance.Dimension

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Table 368 "Dimension Selection Buffer" (relates to)Dimension Selection BufferWork with dimensions to track and analyze data (Learn pages)Work with dimensions to trac…

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.Dimension · captioned “Dimension Selection” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dimension Selection
SourceTable Dimension Selection Buffer
PageType List

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Control1 Level Level Specifies the level for the selected dimension. from the table field
Code Code Specifies the code for the selected dimension.
Description Description Specifies a description of the selected dimension.
Dimension Value Filter Dimension Value Filter Specifies the dimension value that the analysis view is based on. from the table field

Procedures

  • GetDimSelBuf(var TheDimSelectionBuf: Record "Dimension Selection Buffer"): Retrieves all dimension selections with their level assignments from the temporary buffer. Transfers complete dimension configuration including levels and filters to calling process.
  • InsertDimSelBuf(NewSelected: Boolean; NewCode: Text[30]; NewDescription: Text[30]; NewDimValueFilter: Text[250]; NewLevel: Option): Adds a dimension to the selection buffer with level assignment and value filtering capabilities. Automatically resolves dimension descriptions and configures lookup tables for various entity types.

Relations

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). 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: "page", object_name: "Dimension Selection-Level"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 2 sources