Table 7152 "Item Analysis View"

Base Application · Microsoft.Inventory.Analysis · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 9370 “Analysis View List Purchase” (2 Learn pages), Page 9371 “Analysis View List Sales” (2), Page 9372 “Analysis View List Inventory” (2).

Properties

Property	Value
Caption	Item Analysis View
DataClassification	CustomerContent
Permissions	TableData “Item Analysis View Entry” = rimd, TableData “Item Analysis View Budg. 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	Analysis Area	Enum “Analysis Area Type”	—	enum Enum 7130 “Analysis Area Type”
2	Code Δ BC28	Code[10]	Specifies a code for the analysis view.	NotBlank
3	Name Δ BC28	Text[50]	Specifies the name of the analysis view.
4	Last Entry No. Δ BC28	Integer	Specifies the number of the last item ledger entry you posted, prior to updating the analysis view.	not editable
5	Last Budget Entry No. Δ BC28	Integer	Specifies the number of the last item budget entry you entered prior to updating the analysis view.	not editable
6	Last Date Updated Δ BC28	Date	Specifies the date on which the analysis view was last updated.	not editable
7	Update on Posting Δ BC28	Boolean	Specifies if the analysis view is updated every time that you post an item ledger entry, for example from a sales invoice.	not editable
8	Blocked Δ BC28	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	Item Filter Δ BC28	Code[250]	Specifies a filter to specify the items that will be included in an analysis view.	TableRelation Table 27 “Item”
10	Location Filter Δ BC28	Code[250]	Specifies a location filter to specify that only entries posted to a particular location are to be included in an analysis view.	TableRelation Table 14 “Location”
11	Starting Date Δ BC28	Date	Specifies the date from which item ledger entries will be included in an analysis view.
12	Date Compression Δ BC28	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 Δ BC28	Code[20]	Specifies one of the four dimensions that you can include in an analysis view.	TableRelation Table 348 “Dimension”
14	Dimension 2 Code Δ BC28	Code[20]	Specifies one of the four dimensions that you can include in an analysis view.	TableRelation Table 348 “Dimension”
15	Dimension 3 Code Δ BC28	Code[20]	Specifies one of the four dimensions that you can include in an analysis view.	TableRelation Table 348 “Dimension”
17	Include Budgets Δ BC28	Boolean	Specifies whether to include an update of analysis view budget entries, when updating an analysis view.
18	Refresh When Unblocked	Boolean	—

Keys

Key1: Analysis Area, Code (clustered)

Procedures

ItemAnalysisViewReset()
CheckDimensionsAreRetained(ObjectType: Integer; ObjectID: Integer; OnlyIfIncludeBudgets: Boolean)
CheckViewsAreUpdated()
ValidateDelete(FieldName: Text)
CopyAnalysisViewFilters(ObjectType: Integer; ObjectID: Integer; AnalysisArea: Integer; AnalysisViewCode: Code[10])
SetUpdateOnPosting(NewUpdateOnPosting: Boolean)

Plus 6 local procedures.

Triggers

OnDelete

Relations

lookup page Page 7151 “Item Analysis View List”
Location Filter: TableRelation Table 14 “Location”
Item Filter: TableRelation Table 27 “Item”
Dimension 1 Code: TableRelation Table 348 “Dimension”
Dimension 2 Code: TableRelation Table 348 “Dimension”
Dimension 3 Code: TableRelation Table 348 “Dimension”

Referenced by

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

Table 5821 “Item Statistics Buffer”: Analysis View Filter
Table 7112 “Analysis Line Template”: Item Analysis View Code
Table 7153 “Item Analysis View Filter”: Analysis View Code
Table 7154 “Item Analysis View Entry”: Analysis View Code
Table 7156 “Item Analysis View Budg. Entry”: Analysis View Code
Table 7159 “Analysis Selected Dimension”: Analysis View Code

Pages and codeunits on this table

Page 7150 “Invt. Analysis View Card” (source table)
Page 7151 “Item Analysis View List” (source table)
Page 7155 “Sales Analysis View Card” (source table)
Page 7156 “Purchase Analysis View Card” (source table)
Page 9370 “Analysis View List Purchase” (source table)
Page 9371 “Analysis View List Sales” (source table)
Page 9372 “Analysis View List Inventory” (source table)
Codeunit 7150 “Update Item Analysis View” (codeunit runs on it)

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 7150 “Update Item Analysis View” (2 calls: CheckViewsAreUpdated → Update, SetUpdateOnPosting → (object))

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