In this article
IC Suite User Mapping
Use this page to create user mapping records for users that belong to other tenants or belong to different environments of the same tenant. These user mapping records are used for checking the user-entity permission access when Multi-Entity Management is used in companies that are part of intercompany partner records.
These user mapping records are used when creating transactions for intercompany partners that use the web services transfer type. The user mapping records serve to help validate whether a user has entity access permission. A complementary user mapping record must be created for the user of the originating and destination companies for entity access to be valid.
Tip: The user mapping is intended for situations where users have different domain accounts, and slight differences exist in the user IDs. If the user IDs are the same across the different domain accounts, the Map to User ID value can be empty.
Create a User Mapping
To create a user mapping record, follow these steps:
- For a user logged on to Microsoft Dynamics 365 Business Central, and open the IC Suite User Mapping page.
- Select New to add a line .
- Specify a user mapping Code and the Description.
- In Map to User ID, specify the user ID for the mapping code. Typically, you specify the ID of the user currently logged in.
- For the complementary user, log on to Microsoft Dynamics 365 Business Central, open the IC Suite User Mapping page, and create a user mapping record with the same Code and the Description. However, for in Map to User ID, specify the user ID of this user.
- On the MEM User Security Setup page set Entity access for the mapped account.
For the user-entity access to be valid, the user mapping code used for both users must be exactly the same value. After the user mapping record is created for both companies, it is used on the IC Suite Partners page when using the Connect to IC Partner action. For a more information and an example, see Intercompany Suite: Overview.
The user mapping records are also used on the Intercompany General Journal, Sales Invoice, and Purchase Order pages when selecting the intercompany partner code. If the same user mapping record code does not exist for both users, it is considered that the users do not have access to entities of the intercompany partner.
Fields
The following field boxes are available:
| Field | Description |
| Code | Specify a unique user mapping code. |
| Description | Specify a description for the user mapping code. |
| Map to User ID | Specify the user ID to have permission to access the entity. |
Actions
The following actions are available:
| Action | Description |
| Actions > IC Suite > Synchronize |
Synchronize User Security to IC Endpoints. As a best practice, if "Disable Auto Synchronization" is set to true, on the Intercompany FastTab of the Multi-Entity Management Setup page, when changes are made to any record on this page, run this action to ensure that all affected Intercompany Suite partners are updated as well. |
