tableInventoryofficial - Microsoftderived - from the source, no model text

Table 7153 "Item Analysis View Filter"

Base Application · Microsoft.Inventory.Analysis

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC282 fields changed
  5. BC29-30unchanged

Neighbourhood 4 connected objects and pages

Table 348 "Dimension" (relates to)DimensionTable 349 "Dimension Value" (relates to)Dimension ValueTable 7152 "Item Analysis View" (relates to)Item Analysis ViewPage 7152 "Item Analysis View Filter" (pages and codeunits on it, 2 links)Item Analysis View Filter

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.Inventory.Analysis · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Item Analysis View Filter
DataClassification CustomerContent

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 Analysis View Code Code[10] — TableRelation Table 7152 “Item Analysis View” (“Item Analysis View”.Code where(“Analysis Area” = field(“Analysis Area”), Code = field(“Analysis View Code”))); NotBlank
3 Dimension Code Δ BC28 Code[20] Specifies a dimension code that the dimension value filter will be linked to. TableRelation Table 348 “Dimension”; NotBlank
4 Dimension Value Filter Δ BC28 Code[250] Specifies the dimension value that the analysis view is based on. TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Dimension Code” = field(“Dimension Code”)))

Keys

  • Key1: Analysis Area, Analysis View Code, Dimension Code (clustered)

Procedures

1 local procedures, no public ones.

Triggers

OnDelete, OnInsert, OnModify, OnRename

Relations

Pages and codeunits on this table

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

Evidence 1 sources