Answered by:
CRM 2013 Business Processes - can they prevent a lead from being qualified?

Question
-
I would like to use Business Processes to prevent a user from qualifying until they have set the value of a two option set to yes.
I have tried making this field, and others, required but it this does not seem to prevent the lead from being qualified and moving to the opportunity stage.
Is this a fault?
Thanks
Peter
Peter
Monday, January 13, 2014 12:15 PM
Answers
-
You could replace the qualify lead button with a custom function / button and configure it to check the value of the field before allowing the qualifying process to proceed.
- Proposed as answer by Donna EdwardsMVP Thursday, January 23, 2014 7:22 PM
- Marked as answer by PeterGleadell Tuesday, January 28, 2014 9:07 AM
Thursday, January 23, 2014 7:21 PM
All replies
-
You could replace the qualify lead button with a custom function / button and configure it to check the value of the field before allowing the qualifying process to proceed.
- Proposed as answer by Donna EdwardsMVP Thursday, January 23, 2014 7:22 PM
- Marked as answer by PeterGleadell Tuesday, January 28, 2014 9:07 AM
Thursday, January 23, 2014 7:21 PM -
Hi Peter,
Can you please provide a screenshot of what you have done so far? When you say required does it mean you made them mandatory?
Cheers,
Venkat
Friday, January 24, 2014 12:02 AM -
It doesn't matter what has been done since the qualify button on the Lead entity does not interact with the fields on the form. One has to replace the OOB qualify button with a dialog or some other customization that first sets or checks the field and then takes the desired action.
- Edited by Donna EdwardsMVP Friday, January 24, 2014 12:23 AM
Friday, January 24, 2014 12:21 AM -
use plugin qualify it work perfectly .
Hope this helps. ----------------------------------------------------------------------- Santosh Bhagat If this post answers your question, please click "Mark As Answer" on the post and "Vote as Helpful"
- Proposed as answer by Mr. Santosh Bhagat Friday, January 24, 2014 4:24 AM
Friday, January 24, 2014 4:24 AM -
Hi
By taking the help of below links you can prevent a lead from being qualified..
1.Create boolean field on lead.
2.Same field create on opportunity.
3.Mapping the field on lead in 1-N Relationship.
4.Create Plugin on Lead for PreValidation Event and on QualifyLead Message.
http://www.zero2ten.com/blog/processing-opportunities-created-after-qualifying-leads-on-the-new-user-experience-forms-in-microsoft-dynamics-crm/
Hope this helps..
http://developersintent.wordpress.com/2013/09/23/controlling-the-lead-qualification-process-in-crm-2013/- Edited by Suresh Sorde Friday, January 24, 2014 4:47 AM
Friday, January 24, 2014 4:46 AM -
Thanks Donna,
I will take your advice to remove the qualify and use the two option set in the business process to call a workflow to qualify the lead only when the the other fields have the correct value.
Peter
Peter
Tuesday, January 28, 2014 9:07 AM -
Hi Venkat,
Thanks for your response.
Based upon another suggestion I will remove the qualify button and use the two option set in the business process to call a workflow to qualify the lead only when the the other fields have the correct value.
Peter
Peter
Tuesday, January 28, 2014 9:09 AM -
Hi Suresh,
Thanks for the advice. I will certainly use this to prevent opportunities being created.
On this occasion, based upon another suggestion, I will remove the qualify button and use the two option set in the business process to call a workflow to qualify the lead only when the the other fields have the correct value.
Peter
Peter
Tuesday, January 28, 2014 9:18 AM