Table 351 "Dimension Value Combination"
Base Application · Microsoft.Finance.Dimension
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Finance.Dimension · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dimension Value Combination |
| 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 | Dimension 1 Code | Code[20] | — | TableRelation Dimension.Code; NotBlank |
| 2 | Dimension 1 Value Code | Code[20] | — | TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Dimension Code” = field(“Dimension 1 Code”), Blocked = const(false))); NotBlank |
| 3 | Dimension 2 Code | Code[20] | — | TableRelation Dimension.Code; NotBlank |
| 4 | Dimension 2 Value Code | Code[20] | — | TableRelation Table 349 “Dimension Value” (“Dimension Value”.Code where(“Dimension Code” = field(“Dimension 2 Code”), Blocked = const(false))); NotBlank |
Keys
- Key1: Dimension 1 Code, Dimension 1 Value Code, Dimension 2 Code, Dimension 2 Value Code (clustered)
Relations
- Dimension 1 Value Code: TableRelation Table 349 “Dimension Value”
- Dimension 2 Value Code: TableRelation Table 349 “Dimension Value”
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: "Dimension Value Combination"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.