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
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
Is it possible to restrict user from creating an account but at the same time allowing them to qualify the lead? I tried to do it with OOB security roles configuration but it is not allowing the users to qualify the leads if we remove the 'Create' rights on account entity.
1. Leave privileges to create accounts.
2. Create real-time workflow that will handle create of accounts and when "Originating Lead" field is blank (that means direct creation of account not through qualification of lead) stop a workflow as "Cancelled" - that will break the save and user will not be able to create account not through qualification of the lead.
I think I was not a bit clear on the requirement that I stated. So here are the details:
1. We do not want the user to create the 'Accounts' directly that is why we have removed the 'Create' rights from the account entity on the security role.
2. We still want that when the user qualifies a lead then an account gets created in the system. If the user is qualifying the lead then he is getting the error obviously because OOB account creation is happening on lead qualification.
Your requirements were clear for me and my answer resolves your requirement. What exactly is not clear for you?
The solution that Andrew Butenko mentioned is the best option, and his solution would suffice your business requirement. However, there is an another way to achieve this, which is using PA. You can create a Automated blank flow, add a trigger of when a record is created, select the environment, select accounts as entity, add a condition step, check and see if Originated Lead field is blank or not. If it is blank add a step to delete a record (cds) and select account as entity add Account ID from trigger step.
This way you will also have a log of what account was created and what details were added to that, in case anything goes wrong you can turn off the flow and can manually create the account with the details from flow run.
I hope this helps. Please let me know if you need any assistance in this matter.
I suggest you implement the solution given by Andrew Buteko, basically you need to write a real-time workflow on Account Record creation and in that workflow you need to add a condition which checks whether Originating Lead attribute has value.
If this attribute is blank then stop the workflow so that new account wont be created manually but it will create while qualifying lead.
If I'm not wrong with requirement understanding I think you want to achieve impersonation while qualifying lead.
Please refer below URL for more information
I would second the solution by Andrew Buteko, as realtime workflow can restrict user from creating new accounts directly if originating lead is blank.
You can simply hide +new create account button from account entity using ribbon workbench. This way you don't have to manipulate security privilege.
Exception to this is that user will still be able to create account from Advanced find.
Not only from advance find but even from all the account lookups as we will still have +new option in those lookups
Even user will be able to create new account using Quick Create option from top toolbar next to advance find hence would not recommend this solution
I agree with you Manoj. Thank you for correcting me.
Based on Andrew solution, I have created step by step article to setup Workflow and end result is as expected.
Dear Hammad, Please follow ablove article to setup the workflow. Please mark this thread verified so that it will be helpful for other community members.
Thank you Andrew!
Business Applications communities