Table 4022 "User Mapping Work"
HybridBaseDeployment · Microsoft.DataMigration
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 1 connected objects and pages
HybridBaseDeployment · Microsoft.DataMigration · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Source User ID | Code[50] | Specifies the user from the on-premises system. via Page 4022 “Migration User Mapping” | DataClassification SystemMetadata |
| 2 | Dest User ID | Code[50] | Specifies the user in the cloud system. via Page 4022 “Migration User Mapping” | TableRelation “User”.“User Name” where(“Authentication Email” = filter(<> ‘’)); DataClassification SystemMetadata |
Keys
- PK: Source User ID (clustered)
Pages and codeunits on this table
- Page 4022 “Migration User Mapping” (source table)
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: "table", object_name: "User Mapping Work"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.