pageFinanceofficial - Microsoftderived - from the source, no model text

Page 538 "Dimension Combinations"

Base Application · Microsoft.Finance.Dimension

Across versions

  1. BC23-27present
  2. BC28declaration changed
  3. BC29-30unchanged

Neighbourhood 3 connected objects and pages

Table 348 "Dimension" (relates to)DimensionCodeunit 9200 "Matrix Management" (calls)Matrix ManagementWork 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 · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dimension Combinations
SourceTable Dimension
PageType Card
UsageCategory Administration
ApplicationArea Dimensions

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
General Show Column Name ShowColumnName Specifies that the names of columns are shown in the matrix window.
Content MatrixForm part Page 9251 “Dimension Combinations Matrix” —

Actions

Group Action ToolTip Runs
Processing Previous Set Go to the previous set of data.
Previous Column Go to the previous column.
Next Column Go to the next column.
Next Set Go to the next set of data.

Procedures

  • SetSelectedRecord(DimensionCombination: Record "Dimension Combination"): Sets the selected dimension combination record for page initialization and context. Used to position the page matrix on a specific dimension combination for focused editing.

Plus 4 local procedures.

Triggers

OnAfterGetRecord, OnOpenPage

Relations

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.

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

Evidence 2 sources