Page 20021 "APIV1 - Dimensions"
APIV1 · Microsoft.API.V1
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
APIV1 · Microsoft.API.V1 · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | ‘dimensions’, Locked = true |
| Extensible | false |
| SourceTable | Dimension |
| PageType | API |
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 |
|---|---|---|---|
| Group | id | Rec.SystemId |
— |
| code | Code | Specifies the code for the dimension. from the table field | |
| displayName | Name | Specifies the dimension code you enter in the Code field. from the table field | |
| lastModifiedDateTime | Last Modified Date Time | — | |
| dimensionValues | part Page 20053 “APIV1 Dimension Values Entity” | — |
Relations
- source table Table 348 “Dimension”
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: "APIV1 - Dimensions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.