Page 600 "IC Dimensions"
Base Application · Microsoft.Intercompany.Dimension
Across versions
- BC23-30present
Neighbourhood 7 connected objects and pages
Base Application · Microsoft.Intercompany.Dimension · captioned “Intercompany Dimensions” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Intercompany Dimensions |
| SourceTable | IC Dimension |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | Dimensions |
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 | Code | Code | Specifies the intercompany dimension code. |
| Name | Name | Specifies the intercompany dimension name | |
| Blocked | Blocked | Specifies that the related record is blocked from being posted in transactions, for example a customer that is declared insolvent or an item that is placed in quarantine. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Functions | Intercompany Dimension Values | View or edit the intercompany dimension values for the current intercompany dimension. | |
| Dimensions Mapping | Open the mapping between the intercompany dimensions and the dimensions of the current company. | Page 656 “IC Mapping Dimension” | |
| Copy from Dimensions | Creates intercompany dimensions from existing dimensions. | Page 705 “IC Dimensions Selector” | |
| Import | Import intercompany dimensions from a file. | ||
| Export | Export intercompany dimensions to a file. | ||
| Synchronization Setup | Open the setup for the synchronization of the dimensions of intercompany. |
Procedures
2 local procedures, no public ones.
Triggers
OnOpenPage
Relations
- source table Table 411 “IC Dimension”
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 428 “IC Mapping” (2 calls:
ExportToXML → GetFeatureTelemetryName,ImportFromXML → GetFeatureTelemetryName) - Codeunit 8703 “Feature Telemetry” (2 calls:
ExportToXML → LogUptake,ImportFromXML → LogUptake) - Codeunit 419 “File Management” (1 call:
ExportToXML → ServerTempFileName)
Documented on Microsoft Learn
- Manage the Intercompany Inbox and Outbox
- Set up intercompany transaction posting
- Post intercompany documents and journals
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). The call sections above are our own, per object, from the BC29 call graph. 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 Dimensions"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.