Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
The customer is experiencing issues with imported customized formats not being visible in all configured environments of Dataverse, despite successful import in one environment.


Reason:
For a custom Dataverse repository to be visible automatically across all deployed environments, it must be configured prior to the deployment phase. Additionally, there is no automated process for a customer Dataverse repository to be present in all environments.


Resolution:

  1. Export the Custom Repository Configuration:
  2. Navigate to the Electronic Reporting workspace in the environment where the configuration is visible.
  3. Export the configuration to an XML file. This file will contain all necessary settings and mappings.
  4. Import the Configuration into New Environments:
  5. In each new environment, go to the Electronic Reporting workspace.
  6. Import the previously exported XML file. This will recreate the Dataverse repository in the new environment.
  7. Automating the Process:
  8. To automate the process of ensuring the Dataverse repository is present in all environments, Power scripts or Azure pipelines are required. This falls outside the scope of Finance support.
If further assistance is needed, please consult with the relevant teams for additional support.