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 am facing this strange issue on the lead qualification.
Scenario 1: When i open any lead record and fill all the data and qualifies the record. The lead gets qualified without any issue.
Scenaio 2 : When i open any lead record and qualify it directly. It gives me the business process error asking me to fill certain mandatory details before qualifying.
After that if i select any of the field which has java scripts written on change of it, it starts to throw error which says that "Reference Error : Function abc is not defined at the eval". Moreover the ribbon above also gets hanged. Even if try to save the for by pressing CTRL+S using keyboard then all the java script functions written on OnSave of the form throws the reference error.
But later if i try to refresh the page and try to fill all the details, it works fine and the form also gets qualified without any issue.
Conclusion : Error occurs only when i click on Qualify button when all the mandatory details for qualification are not filled.
Also i tried disabling all the plugins that was on create and update of the Lead, but it works the same.
Similarly when i try to import the lead solution to check if there is other validations written on qualify button in Ribbon workbench, then i could not see the qualify button in the Bar as shown below.
This seems to be really strange and i dont know how to proceed further. Please help me with some suggestions.
The Qualify ribbon in Ribbon workbench is named as "ConvertLeadQuick".
We could find its ID in F12 develop tools in browser.
That was really helpful and i could locate my Qualify button on the Ribbon now. I could actually see 2 Qualify button (ConvertLeadQuick and ConvertLeadQuick.Web) performing the same set of work in my instance.
Still this issue persist.
Once i qualify, the entire scripts starts throwing error and the ribbon also hangs and i could then see 2 Disqualify button.
It's really strange.
I created a lead in my instance with only 2 required fields and qualified it directly, and it worked successfully.
Please check if there is any business rules , required fields in BPF or plug-ins which may effect this function.
If this issue still exists, I recommend you to raise a ticket to Microsoft Support Team to let the engineers help you remotely.
Thank you for your quick response.
I even tried to create a trial instance to compare and check if Qualify has all the inbuilt Mscrm rules in it and it is all the same. I would do a little more trouble shooting before raising a ticket to Microsoft.
Let me know if you get any further ideas for troubleshooting :)
In order to qualify the lead, you need to verify that there should be two buttons to Qualify - ConvertLeadQuick, ConvertLeadQuick.Web.
Both the buttons should have script ‘MarketingSales/Lead/Lead_main_system_library.js’ with function as ‘Mscrm.LeadCommandActions.qualifyLeadQuick’. But if you are missing this script within the command for Qualify button then you should raise a Microsoft Ticket for this issue. Since it is an OOB ribbon button on Lead entity, they would assist you in order to resolve the issue.
Also, if in your CRM, Project Service Automation(PSA) is installed then refer the below link:
That is a great information.
I was verifying the same in the ribbon workbench.
Currently the instance what i am using is not UCI enabled according to your information i have these functions on both buttons.
This Qualify button has Enable Rule as Mscrm.Form.Lead.IsNotUCI and have script ‘MarketingSales/Lead/Lead_main_system_library.js’ but with function as Mscrm.LeadCommandActions.qualifyLeadQuick
This Qualify button has Enable Rule as Mscrm.Form.lead.IsNotUCI and have script ‘MarketingSales/Lead/Lead_main_system_library.js’ but with function as Mscrm.LeadCommandActions.qualifyLeadQuick
The function on both the button is same as you have mentioned but if i notice i could see both the qualify button has same enable rule i.e. IsNotUCI.
I tried to check the same with my Trial instance which has the enable rules of IsUCI and IsNotUCI as the way you mentioned above. I could see this discrepancy here.
The lead gets qualified when there is no customization. It causes issue only when i impose plugin customization to it.
I am writing a plugin to restrict the user from qualifying a lead without filling 2 fields. I tried to use the same plugin for my trial instance and it works as expected but when i register the same plugin in my development instance it hangs the form.
Will be because of anything else that i couldn't notice? I feel microsoft wont help me in this as their buttons work when customization are removed.
Kindly help me out with any perspective for testing or troubleshooting.
Business Applications communities