Views:

Applies to Product - Dynamics 365 Finance


What’s happening?
Customers encounter errors during dual-write operations in Dynamics 365 and Dataverse environments. The errors include:

  1. "Couldn't resolve the guid for the field: teamid.businessUnit. The lookup value was not found."
  2. "Dual-write application configuration failed. RetrievePrivilegeForUser: The user has not been assigned any roles. They need a role with the prvReadSolution privilege."

 

Reason:
These occur due to the following reasons:

  1. Dual-write uses the default team of the mapped (or root) business unit as the owner of the record to be imported. The expectation is that the name of the default team matches the business unit name. If the default team's name is changed after establishing projects or dual-write links, data ingestion fails with the mentioned error.
  2. The user involved in dual-write configuration does not have the required security role with the prvReadSolution privilege assigned.

 

Resolution:
Issue 1: Couldn't resolve the guid for the field: teamid.businessUnit

  • Navigate to the Power Platform Admin Center: https://admin.powerplatform.microsoft.com
  • Select the environment experiencing the issue.
  • Go to Settings > Users + Permissions > Teams.
  • Verify if the Team Name and Business Unit names differ.
  • In Customer Engagement (CE), open the Business Unit, rename it, then change it back to the original name and save again. This action refreshes the Team Name to match the Business Unit.
  • Retry the initial synchronization.
Issue 2: Dual-write application configuration failed due to missing user roles
  • Identify the user using the provided user ID from the error message in the Dataverse environment.
  • Assign the required security role with the prvReadSolution privilege:
  • Log in to the Power Platform Admin Center: https://admin.powerplatform.microsoft.com/environments.
  • Select the environment associated with Dataverse.
  • Navigate to the Access tab and click See all under Users.
  • Find the user using the provided ID and assign a security role that includes the prvReadSolution privilege.
  • After assigning the necessary role, return to the Lifecycle Services (LCS) environment page and click on "Resume Dual-write application" to retry the configuration.