Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
The global configuration repository is not opening on the UAT environment, and users encounter an error message indicating a failure in the request to Dataverse. The error specifies that the user has not been assigned any roles necessary to access the required Dataverse tables.


Reason:
The underlying cause of this is that the user associated with the specified ID does not have the necessary permissions, specifically lacking a role that includes the privilege prvReadmsdyn_ElectronicReportingConfigurationsIndexFile.


Resolution:

  1. Check User Roles:
  2. Go to your Dataverse environment and check the roles assigned to the user with the specified ID.
  3. Ensure that the user has at least one role that includes the privilege prvReadmsdyn_ElectronicReportingConfigurationsIndexFile.
  4. Assign the Necessary Role:
  5. If the user does not have the required role, assign them a role that includes the necessary privileges. You may need to create a custom role if no existing role has the required privileges.
  6. Verify Solution Installation:
  7. Ensure that the solution containing the ElectronicReportingConfigurationsIndexFile table is installed in the UAT environment.
  8. Check Application User Access:
  9. If an application user is being used, ensure that it has the correct roles and privileges assigned.
  10. Re-Test Access:
  11. After updating the roles, try accessing the global configuration repository again to see if the issue is resolved.
  12. Log Activities:
  13. If issues persist, consider checking logs for additional error messages or contacting your system administrator for further assistance.
  14. If the issue is still not resolved:
  15. In the Dataverse environment, remove both the managed and unmanaged solutions. First, remove the managed solution ERReports, ensuring it is removed together with its artifacts.
  16. If the artifacts are not removed when the unmanaged solution is being removed, it is required to remove them manually first. Remove the records from the Electronic Reporting Configuration File and Electronic Reporting Configurations Index File tables, which belong to the unmanaged solution.
  17. Update the Globalization Solution for Microsoft Dynamics 365 Finance package to the latest available version in the FnO environment.
  18. Remove the previously created Dataverse repositories and create a new Dataverse repository, specifying a new solution name. Open it and ensure that there is a Bill of Lading (Excel) configuration located in Dataverse.