1. Data Management
  2. Master Data Management Studio
  3. Setting up MDM studio

Exchange MDM studio configuration

You can exchange master data management configurations between environments for D365 F&SCM. To do so, you export the desired master data management configurations to an XML file and import these files in another D365 F&SCM environment.


Application Consultant Application Consultant Start Start Export Connectivity studio configuration Export Connectivity studio configuration In MDM studio, to send data from a source company to a target company, Connectivity studio messages are used. You define the applicable messages on a master data entity or on the related hierarchy messages. When you import master data entities into another D365 F&SCM environment, ensure that the related Connectivity studio messages already exist. So, when you export master data entities, ensure to export the related Connectivity studio messages as well. For more information, refer to Export Connectivity studio configuration. Export company configuration Export company configuration You can export an MDM company configuration to an XML file. So, you can import it in another D365 F&SCM environment. If you export a company configuration, depending on the company type, these settings of these fields are included: Type Exported Data Notes Standard Type   Company accounts ID Only the company account ID is exported. The related legal entity is not exported. Data stewards Name Email address Only the user ID is exported. The related user is not exported. External Type   ID   Data stewards Name Email address Only the user ID is exported. The related user is not exported. Target group Type   ID   Target companies - Name A target company refers to an MDM company. In the export, you can optionally include the MDM companies to which the target companies refer. If you do so, only the company account IDs are exported. The related legal entities are not exported. Hierarchy Type   ID   Organization hierarchy Only the organization hierarchy ID is exported. The related organization hierarchy is not exported. Procedure 1. Click Master data management - Setup. 2. Click the Companies tab. 3. In the list, find and select the desired company. 4. Click Edit. 5. On the Company page, on the Action Pane, click Deploy. 6. Click Export company to file. 7. In the Download file field, type a value. Note: You are advised to always include '.xml' in the export file name. 8. You can run the export of companies in the background. While the export runs, you can continue with other activities in the environment. Select Yes in the Run in background field. Note: You can only run the export in the background if you export one company. If several companies are selected, automatically, the Run in background field is set to No and disabled. 9. Click Include companies. 10. In the list, find and select the desired companies. 11. Click OK. Note: If the export is not run in the background, the export file is downloaded automatically to your local downloads location. 12. Sub-task: Get export file. 13. On the Action Pane, click Deploy. 14. Click Download transactions. 15. In the list, find and select the desired record. 16. Click Download. 17. Close the page. 18. Close the page. Export master data entity configuration Export master data entity configuration You can export a master data entity configuration to an XML file. So, you can import it in another D365 F&SCM environment. If you export a master data entity configuration, depending on the setup, this is included: General master data entity settings. Custom settings. All defined master data entity message records. Note: Only the references to the Connectivity studio messages are exported. The referenced Connectivity studio messages are not exported. All defined hierarchy message records. Note: Only the references to the Connectivity studio messages are exported. The referenced Connectivity studio messages are not exported. Display field and range settings. All defined validations. All defined dynamic form setup records. Procedure 1. Click Master data management - Setup. 2. On the Master data entities tab, in the list, find and select the desired master data entity. 3. Click Edit. 4. On the Master data entities page, on the Action Pane, click Deploy. 5. Click Export master data entity to file. Note: You can export only one master data entity at a time. 6. In the Download file field, type a value. Note: You are advised to always include '.xml' in the export file name. 7. Select No in the Run in background field. 8. Click OK. Note: If the export is not run in the background, the export file is downloaded automatically to your local downloads location. 9. Sub-task: Get export file. 10. On the Action Pane, click Deploy. 11. Click Download transactions. 12. In the list, find and select the desired record. 13. Click Download. 14. Close the page. 15. Close the page. Event Event Import Connectivity studio configuration Import Connectivity studio configuration In MDM studio, to send data from a source company to a target company, Connectivity studio messages are used. You define the applicable messages on a master data entity or on the related hierarchy messages. When you import master data entities into another D365 F&SCM environment, ensure that the related Connectivity studio messages already exist. To facilitate a smooth import process, make sure to import the related Connectivity Studio messages before you import the master data entities. For more information, refer to Import Connectivity studio configuration. Import company configuration Import company configuration You can import an MDM company configuration from an XML file. Usually, the company configuration in the import file is exported from another D365 F&SCM environment. If you import a company configuration, depending on the company type, these conditions and actions apply: Type Condition Action Standard Company accounts ID must be specified in import file. An MDM company is imported only if the related legal entity exists in the import environment. Note: Legal entities are not imported with an MDM company import. Data stewards are optional. A data steward is imported only if the related user exists in the import environment. Note: Users are not imported with an MDM company import. External ID must be specified in import file.   Data stewards are optional. A data steward is imported only if the related user exists in the import environment. Note: Users are not imported with an MDM company import. Target group ID must be specified in import file.   Target companies are optional. In the import file, target companies can be specified for the target group. A target company refers to an MDM company. Target group import is done in this sequence: A target company refers to an MDM company. The import file can include the MDM companies to which the target companies refer. If so, import these MDM companies. An MDM company is imported only if the related legal entity exists in the import environment. Import the target group. For the target group, set the target company references to the MDM companies. Note: Legal entities are not imported with an MDM company import. Hierarchy ID must be specified in import file.   Organization hierarchy reference must be specified in import file. In the import file, an organization hierarchy reference can be specified for the hierarchy. A hierarchy is imported only if the referenced organization hierarchy exists in the import environment. Note: Organization hierarchies are not imported with an MDM company import. Procedure 1. Click Master data management - Setup. 2. Click the Companies tab. 3. Click Edit. 4. On the Action Pane, click Deploy. 5. Click Import company from file. 6. Click Select configuration to browse for the desired company configuration XML file and select it for import. 7. An imported MDM company can exist in the import environment. You can choose to overwrite existing MDM companies with those from the import file. Select Yes in the Overwrite existing companies field. Note: If you overwrite an existing MDM company with: Data stewards defined, the existing data stewards setup is deleted. Target companies defined, the existing target companies setup is deleted. 8. Select Yes in the Run in background field. 9. Click OK. 10. Close the page. Import master data entity configuration Import master data entity configuration You can import a master data entity configuration from an XML file. Usually, the master data entity configuration in the import file is exported from another D365 F&SCM environment. If you import a master data entity configuration, these conditions and actions apply: Condition Action The Master data type ID field must have a value in the import file. If no Master data type ID is defined, no import is done. The imported master data entity does not exist in the import environment If the imported master data entity already exists in the import environment, you get a prompt whether you want to override the existing master data entity. The referenced Connectivity studio messages exist in the import environment If a referenced Connectivity studio message does not exist, you get a prompt whether you want to continue the import. If you click: No, the master data entity is not imported. Yes, the master data entity import continues and the master data entity message record is created without the Connectivity studio message defined. In this case, you must manually complete the setup of the master data entity. Note: Only the references to the Connectivity studio messages are imported. The referenced Connectivity studio messages are not imported. The referenced MDM companies exist in the import environment If a referenced source MDM company or target MDM company does not exist in the import environment, you get a prompt whether you want to continue the import. If you click: No, the master data entity is not imported. Yes, the master data entity import continues and the master data entity message record is created without the missing MDM company defined. In this case, you must manually complete the setup of the master data entity. Note: Only the references to the MDM companies are imported. The referenced MDM companies are not imported. Procedure 1. Click Master data management - Setup. 2. On the Master data entities tab, click Edit. 3. On the Action Pane, click Deploy. 4. Click Import master data entity from file. 5. Click Select configuration to browse for the desired master data entity configuration XML file and select it for import. 6. Select or clear the Run in background check box. 7. Click OK. 8. Close the page. End End

Activities

Name Responsible Description

Export Connectivity studio configuration

Application Consultant

In MDM studio, to send data from a source company to a target company, Connectivity studio messages are used. You define the applicable messages on a master data entity or on the related hierarchy messages.

When you import master data entities into another D365 F&SCM environment, ensure that the related Connectivity studio messages already exist.

So, when you export master data entities, ensure to export the related Connectivity studio messages as well.

For more information, refer to Export Connectivity studio configuration.

Export company configuration

Application Consultant

You can export an MDM company configuration to an XML file. So, you can import it in another D365 F&SCM environment.

If you export a company configuration, depending on the company type, these settings of these fields are included:

Type Exported Data Notes
Standard Type  

Company accounts ID

 Only the company account ID is exported. The related legal entity is not exported.

Data stewards
  • Name
  • Email address

Only the user ID is exported. The related user is not exported.
External Type  
ID  

Data stewards
  • Name
  • Email address

Only the user ID is exported. The related user is not exported.
Target group Type  
ID  
Target companies - Name A target company refers to an MDM company. In the export, you can optionally include the MDM companies to which the target companies refer. If you do so, only the company account IDs are exported. The related legal entities are not exported.
Hierarchy Type  
ID  

Organization hierarchy

 Only the organization hierarchy ID is exported. The related organization hierarchy is not exported.

Export master data entity configuration

Application Consultant

You can export a master data entity configuration to an XML file. So, you can import it in another D365 F&SCM environment.

If you export a master data entity configuration, depending on the setup, this is included:

  • General master data entity settings.
  • Custom settings.
  • All defined master data entity message records.
    Note: Only the references to the Connectivity studio messages are exported. The referenced Connectivity studio messages are not exported.
  • All defined hierarchy message records.
    Note: Only the references to the Connectivity studio messages are exported. The referenced Connectivity studio messages are not exported.
  • Display field and range settings.
  • All defined validations.
  • All defined dynamic form setup records.

Import Connectivity studio configuration

Application Consultant

In MDM studio, to send data from a source company to a target company, Connectivity studio messages are used. You define the applicable messages on a master data entity or on the related hierarchy messages.

When you import master data entities into another D365 F&SCM environment, ensure that the related Connectivity studio messages already exist.

To facilitate a smooth import process, make sure to import the related Connectivity Studio messages before you import the master data entities.

For more information, refer to Import Connectivity studio configuration.

Import company configuration

Application Consultant

You can import an MDM company configuration from an XML file. Usually, the company configuration in the import file is exported from another D365 F&SCM environment.

If you import a company configuration, depending on the company type, these conditions and actions apply:

Type Condition Action
Standard Company accounts ID must be specified in import file.

An MDM company is imported only if the related legal entity exists in the import environment.

Note: Legal entities are not imported with an MDM company import.
Data stewards are optional.

A data steward is imported only if the related user exists in the import environment.

Note: Users are not imported with an MDM company import.
External ID must be specified in import file.  
Data stewards are optional.

A data steward is imported only if the related user exists in the import environment.

Note: Users are not imported with an MDM company import.
Target group ID must be specified in import file.  
Target companies are optional.

In the import file, target companies can be specified for the target group. A target company refers to an MDM company.

Target group import is done in this sequence:

  1. A target company refers to an MDM company. The import file can include the MDM companies to which the target companies refer. If so, import these MDM companies. An MDM company is imported only if the related legal entity exists in the import environment.
  2. Import the target group.
  3. For the target group, set the target company references to the MDM companies.

Note: Legal entities are not imported with an MDM company import.
Hierarchy ID must be specified in import file.  
Organization hierarchy reference must be specified in import file.

In the import file, an organization hierarchy reference can be specified for the hierarchy. A hierarchy is imported only if the referenced organization hierarchy exists in the import environment.

Note: Organization hierarchies are not imported with an MDM company import.

Import master data entity configuration

Application Consultant

You can import a master data entity configuration from an XML file. Usually, the master data entity configuration in the import file is exported from another D365 F&SCM environment.

If you import a master data entity configuration, these conditions and actions apply:

Condition Action
The Master data type ID field must have a value in the import file. If no Master data type ID is defined, no import is done.
The imported master data entity does not exist in the import environment If the imported master data entity already exists in the import environment, you get a prompt whether you want to override the existing master data entity.
The referenced Connectivity studio messages exist in the import environment

If a referenced Connectivity studio message does not exist, you get a prompt whether you want to continue the import. If you click:

  • No, the master data entity is not imported.
  • Yes, the master data entity import continues and the master data entity message record is created without the Connectivity studio message defined. In this case, you must manually complete the setup of the master data entity.

Note: Only the references to the Connectivity studio messages are imported. The referenced Connectivity studio messages are not imported.
The referenced MDM companies exist in the import environment

If a referenced source MDM company or target MDM company does not exist in the import environment, you get a prompt whether you want to continue the import. If you click:

  • No, the master data entity is not imported.
  • Yes, the master data entity import continues and the master data entity message record is created without the missing MDM company defined. In this case, you must manually complete the setup of the master data entity.

Note: Only the references to the MDM companies are imported. The referenced MDM companies are not imported.

Provide feedback