Page 9371 "Analysis View List Sales"

Base Application · Microsoft.Sales.Analysis · captioned “Sales Analysis Views” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Sales Analysis Views
SourceTable	Item Analysis View
PageType	List
UsageCategory	ReportsAndAnalysis
ApplicationArea	Dimensions, SalesAnalysis

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	Code	Code	Specifies a code for the analysis view.
	Name	Name	Specifies the name of the analysis view.
	Include Budgets	Include Budgets	Specifies whether to include an update of analysis view budget entries, when updating an analysis view.
	Last Date Updated	Last Date Updated	Specifies the date on which the analysis view was last updated.
	Dimension 1 Code	Dimension 1 Code	Specifies one of the four dimensions that you can include in an analysis view.
	Dimension 2 Code	Dimension 2 Code	Specifies one of the four dimensions that you can include in an analysis view.
	Dimension 3 Code	Dimension 3 Code	Specifies one of the four dimensions that you can include in an analysis view.

Actions

Group	Action	ToolTip	Runs
Analysis	Filter	Apply the filter.	Page 7152 “Item Analysis View Filter”
Processing	Edit Analysis View	Edit the settings for the analysis view such as a column or line.
	Update	Get the latest entries into the analysis view.	Codeunit 7150 “Update Item Analysis View”

Relations

card page Page 7155 “Sales Analysis View Card”
source table Table 7152 “Item Analysis View”

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