Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I created Power Automate to import customer data on SQL server on premise into D365 sales contact entity, then this error happens when create new entry on CDS.
"Principal user (Id=89842c10-06df-4770-8a7a-c9c95c401147, type=8, roleCount=2, privilegeCount=563, accessMode=1(Setup/Stub user with filtered privileges from associated roles. Consider changing user AccessMode to Full (without privilege filtering))), is missing prvReadContact privilege (Id=ba09ec92-12c4-4312-ba16-5715c2cbd6da) on OTC=2 for entity 'contact'. context.Caller=776f149d-7527-ea11-a812-000d3a519cc2"
I checked about the user who runs PowerAutomate.
Any idea to check further more?
Thanks for reaching Dynamics community. I hope the user account being used for Power Automate is not a guest user on to the Azure AD tenant where this target CDS environment belongs.
How about testing this after creating a new user account from Office 365 with D365 CE license along with a System Admin security role on CRM online?
Let me know if this works. Please mark my comment as answered if this helps. :-)
Much apprecited your suggestion! I thoroughly looked into my FLOW and found I attempted to insert invalid value into lookup field. I fixed value on my SQL server that is data source and run the FLOW flawless.
Business Applications communities