Page 667 "IC Mapping Dimension Outgoing"
Base Application · Microsoft.Intercompany.Dimension
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Intercompany.Dimension · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| SourceTable | Dimension |
| PageType | ListPart |
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 |
|---|---|---|---|
| Lines | Dim. Code. | Code | Specifies the dimension code. |
| Dim. Name | Name | Specifies the dimension name. | |
| IC Dim. Code | Map-to IC Dimension Code | Specifies the intercompany’s dimension code associated with the dimension of the current company. |
Procedures
GetSelectedLines(var Dimensions: Record Dimension): Retrieves the currently selected dimension lines for processing.
Relations
- source table Table 348 “Dimension”
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 Mapping Dimension Outgoing"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.