#Configure Mapping Settings

Configure mapping settings for the organizations/environments that work as the source and the destination in an out-of-place restore to ensure data integrity in the destination after the restore job.

You can only add one mapping for the same pair of source and destination. Follow the steps below to add and configure a mapping:

1. Navigate to Settings > Mapping.

2. Click the Add mapping button. The Add mapping panel appears.

3. Select the source and destination for the mapping.

4. Click Save.

5. In Step 1, click Generate to generate a mapping template. Cloud Backup for Dynamics 365 will scan your source and destination organizations/environments and automatically map the data in the source and destination.

   The mapping template generation may take a while. You can monitor the progress through the Job monitor. The mapping generation status and finished time will be displayed next to the Generate button after it is finished.

6. After the generation, click the Download link to download the generated mapping template. An Excel file will be downloaded to your local computer.

   This file provides a General Information sheet to show the source and destination organizations/environments that this mapping is for and provides instructions on how to configure the mapping in this file and the additional notes you need to pay attention to. Follow the instructions in Excel to complete the mappings and import the mapping back.

   • Each sheet in this file named after an entity contains the automatically detected mappings for this entity in the source and destination, displayed in the Source GUID, Source Name, Destination GUID, and Destination Name columns. You may find empty cells in the Destination GUID column and Destination Name column if there is no matching name in the destination or more than one. You can search or filter the data in Data in the Destination sheet and complete the mapping.

   • If you didn’t find the proper data in the Data in Destination sheet, you can copy the source GUID and source name to the Destination GUID and Destination Name columns to try to create them in the restore job.

   • Note the following when editing the mapping template:

     • Keep the General Information sheet intact and first.

     • If you need to add mappings for an entity that is not in this mapping template file, you can add a new sheet for it and enter its mappings in the same data format as the others.

     • Do not delete or rename any datasheets, and do not delete any records listed in Source GUID and Source Name.

     • Only the data in Source GUID, Source Name, Destination GUID, and Destination Name will be imported and verified.

     • Ensure there are no empty cells for Destination GUID and Destination Name in the mapping before you import this mapping file.

     • There are four basic entities in the Dynamics 365 organization that we recommend restoring to the destination first before out-of-place restoring the others. For details, refer to Mapping Settings for the Basic Entities.

7. After you complete the mapping settings in the file, go back to the Settings > Mapping page in the Cloud Backup for Dynamics 365 interface.

8. Find your mapping in the table. The mapping status is Pending mapping import. Edit the mapping. The Edit mapping panel appears.

9. Go to Step 2 and click the Upload.

10. Browse the mapping file and click Open. Cloud Backup for Dynamics 365 will import the mappings from the selected file and verify the mapping settings. The errors detected will be displayed in the table. If there are no errors in the mapping, the mapping status will be updated to Active.

    Note that only the mappings with the Active status can be used in the out-of-place restore.

#Mapping Settings for the Basic Entities

Refer to the section below for the mapping settings for System User, Business Unit, Currency, Unit, and Unit Group.

• System User – The user cannot be manually created in Dynamics 365 CRM. If a user has been added into multiple organizations/environments, this user will have a different GUID in each organization/environment.

  The generation of the mapping template can automatically map the users with the same name in the source and destination. For the mappings of the other system users, you can choose a destination user as the default user if your destination does not have many system users. You can map all the other source users to this default user if you desire.

  For instance, the source has account A, whose owner is user A, and account B, whose owner is user B. If you map both user A and user B to the destination user D, the owner of account A and account B will be restored to user D.

• Business Unit – The root Business Unit cannot be restored to the destination. You must find the destination root Business Unit and enter its GUID and name to the Destination GUID and Destination Name column. For the other business units, you can copy the source GUID and name to the destination area to let the restore job create them in the destination.

  For instance, Source Root BU is the root Business Unit in the source, and it is the parent Business Unit of BU A. The Destination Root BU is the root Business Unit in the destination. When configuring the mapping, you must map the Source Root BU to the Destination Root BU, and you can copy the source GUID and name of BU A to the destination area. Therefore, when you select BU A to restore, the restore job will create BU A in the destination with the same GUID and name, and its parent Business Unit is Destination Root BU.

• Currency – The base currency in the source and destination must be the same. Otherwise, the value in a different unit of currency would be incorrect. To configure the mapping, enter the GUID and name of the same currency in the destination. If the destination does not have that currency, copy the source GUID and name to the destination area. Restore job will create the currency if the destination GUID does not exist and skip restoring the currencies if the destination GUID can be found.

• Unit and Unit Group – Each Unit Group will have a Primary Unit automatically created. Dynamics 365 cannot keep the same GUID for the Primary Unit when the restore job creates the Primary Unit in the destination. Therefore, you must map the Primary Unit of each Unit Group in the source and destination. For the other units, you can copy the source GUID and name to the destination area to let restore jobs create them in the destination.

  You can choose one of the following methods to map and restore the Units and Unit Groups:

  • Scenario 1 – Not too many Units and Unit Groups in your environment.

    • If there are not too many Units and Unit Groups in your environment, we recommend manually creating the Unit Groups and their Primary Units in the destination using the same name as the source.

    • Configure the mapping settings and generate the mapping template. The mapping template will automatically map those Units and Unit Groups. For the other units, you can copy the source GUID and name to the destination area and then import the mapping file.

    • Select the Unit entity to perform an out-of-place restore.

  • Scenario 2 – Many Units and Unit Groups need to restore to the destination.

    • Configure the mapping settings for the source and destination and generate the mapping template.

    • Copy the source GUID and name to the destination area for the Unit Groups and Units that have empty cells. Complete the mappings and import the mapping file back.

    • Select the Unit Group entity to perform an out-of-place restore. The Unit Groups are restored to the destination with Primary Units automatically created. These Primary Units use a different GUID than the source.

    • Go to Mapping Settings to generate the mapping again. Map the destination Primary Units created by the restore job to the source Primary Units in the Unit sheet and import the mapping file back.

    • Select the Unit entity to perform an out-of-place restore.