Browser's network log shows the following error:
{"error":{"code":"0x80040220","message":"Principal user (Id=c4491930-07ca-ec11-a7b5-0022482b21d5, type=8, roleCount=8, privilegeCount=350, accessMode=0), is missing prvReadsales_linkedin_users_signedin_status privilege (Id=d72f0f64-7c07-4637-8ee9-333d9bb8ee64) on OTC=10605 for entity 'sales_linkedin_users_signedin_status' (LocalizedName='sales_linkedin_users_signedin_status'). context.Caller=c4491930-07ca-ec11-a7b5-0022482b21d5","@Microsoft.PowerApps.CDS.ErrorDetails.ApiExceptionSourceKey":"Plugin/Microsoft.Crm.ObjectModel.CustomBusinessEntityService","@Microsoft.PowerApps.CDS.ErrorDetails.ApiStepKey":"101c6e07-de04-ed11-82e4-000d3a996b8f","@Microsoft.PowerApps.CDS.ErrorDetails.ApiDepthKey":"1","@Microsoft.PowerApps.CDS.ErrorDetails.ApiActivityIdKey":"9370a38b-0f61-44b3-bf96-856c6d99fd07","@Microsoft.PowerApps.CDS.ErrorDetails.ApiPluginSolutionNameKey":"System","@Microsoft.PowerApps.CDS.ErrorDetails.ApiStepSolutionNameKey":"System","@Microsoft.PowerApps.CDS.ErrorDetails.ApiExceptionCategory":"ClientError","@Microsoft.PowerApps.CDS.ErrorDetails.ApiExceptionMessageName":"PrivilegeDenied","@Microsoft.PowerApps.CDS.ErrorDetails.ApiExceptionHttpStatusCode":"403","@Microsoft.PowerApps.CDS.ErrorDetails.0":"prvReadsales_linkedin_users_signedin_status","@Microsoft.PowerApps.CDS.ErrorDetails.1":"sales_linkedin_users_signedin_status","@Microsoft.PowerApps.CDS.HelpLink":http://go.microsoft.com/fwlink/?LinkID=398563&error=Microsoft.Crm.CrmException%3a80040220&client=platform,"@Microsoft.PowerApps.CDS.InnerError.Message":"Principal user (Id=c4491930-07ca-ec11-a7b5-0022482b21d5, type=8, roleCount=8, privilegeCount=350, accessMode=0), is missing prvReadsales_linkedin_users_signedin_status privilege (Id=d72f0f64-7c07-4637-8ee9-333d9bb8ee64) on OTC=10605 for entity 'sales_linkedin_users_signedin_status' (LocalizedName='sales_linkedin_users_signedin_status'). context.Caller=c4491930-07ca-ec11-a7b5-0022482b21d5"}}
Cause:
Dynamics 365 has added a new privilege: prvReadsales_linkedin_users_signedin_status
Users will face this issue especially when using only custom security roles in the organization. Custom security roles do not get auto-updated when Dynamics 365 updates are pushed by Microsoft.
Resolution:
We can create a new security role Sales LinkedIn User and assigned it to all the users. Provide user level read privilege on sales_linkedin_users_signedin_status
Expected result:
Hi Gaurav Tempe,
Thanks for sharing this information. It's really helpful.