Page 652 "IC Document Dimensions"
Base Application · Microsoft.Intercompany.Dimension
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Intercompany.Dimension · captioned “Intercompany Document Dimensions” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Intercompany Document Dimensions |
| SourceTable | IC Document Dimension |
| PageType | List |
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 | Dimension Code | Dimension Code | Specifies the dimension. |
| Dimension Value Code | Dimension Value Code | Specifies the dimension value. |
Procedures
2 local procedures, no public ones.
Relations
- source table Table 442 “IC Document 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: "IC Document Dimensions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.