Share
ReportHi all,
Most of you know that there are big differences between 2016 BPF and 365 BPF, and one of them is the change of how to handle security role. It is fine if you create BPF in 365 but if you create BPF in 2016, (even for built-in BPF such as Lead to Opportunity Sale Process) as soon as you enable some custom security roles using "Enable Security Roles" button (this is replaced by "Edit Security Roles" in 365), and then migrate to 365, you will not be able to delete those security roles because CRM 365 thought the BPF still depend on these security roles EVEN THOUGH when open those security roles' "Business Process Flows" tab, those roles don't have any privilege to the BPF at all.
However, when I query the database, I found that the BPF's ProcessRoleAssignment field still have the old legacy references to the security roles ids and this may cause CRM 365 mistakenly think the BPF still depend on those security roles. And since the "Enable Security Roles" button is replaced, I cant no longer be able to remove those dependent security roles, therefore, they can't be deleted. The only way now is to use SQL query to update the ProcessRoleAssignment field.
Main question, is there other way to fix this issue without modifying database using query?
Thanks,
Sam
*This post is locked for comments
All responses (
Answers (
223
