Page 4022 "Migration User Mapping"
HybridBaseDeployment · Microsoft.DataMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
HybridBaseDeployment · Microsoft.DataMigration · captioned “Define User Mappings” · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Define User Mappings |
| SourceTable | User Mapping Work |
| PageType | NavigatePage |
| UsageCategory | Tasks |
| Permissions | tabledata “My Notifications” = RIMD, tabledata “User” = RIMD, tabledata “Hybrid Company Status” = RIM |
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 |
|---|---|---|---|
| UserList | On-Premises User | Source User ID | Specifies the user from the on-premises system. |
| Cloud User | Dest User ID | Specifies the user in the cloud system. |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | OK | OK | |
| Cancel | Cancel |
Events published
OnSkipUserRenameCommit(var SkipUserRenameCommit: Boolean)(integration)
Procedures
WarnUserMappingDoneBefore()UpdateSetupRecord()
Plus 4 local procedures.
Triggers
OnOpenPage
Relations
- source table Table 4022 “User Mapping Work”
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 4001 “Hybrid Cloud Management” (1 call:
OnOpenPage → SendRecordLinkMigrationNotification) - Codeunit 9800 “User” (1 call:
ProcessUserMapping → RenameUser)
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: "Migration User Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.