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
leads can be automatically created from a third party source. Sometimes this third party source doesn't populate all required fields that we normally ask for.
What is the easiest way to let people still disqualify leads without them populating all required fields?
Solutions that I currently see:
Are there any other (simpler) solutions?
In my organization we categorize all leads received through a third party with a 'Lead Source' option set. This then allows us to set field requirements using business rules instead of the static field requirements.
If you want more information for business rules, check the below link:
I don't see this as a solution to my issue.
When Leads are qualified, all required fields should still be entered.
And sometimes that information is also provided by the third party system. So just making the fields not required when the Lead is imported, doesn't solve the issue.
Only when disqualifying the required fields should not be needed.
I guess a solution could be:
- Create own button
- Disqualify Lead using Web API and refresh Form
Any other ideas?
did you find a solution? Because we have the same problem. Our Sales wish to disqualify Leads faster without filling out all required fields.
Use the business rule suggestion by Trustin and combine it with other tools.
For example you could add a new field to toggle for "disqualify" and incorporate it in Trustin's suggestion so setting the toggle to "disqualify" would be the trigger that removes the requirement to satisfy those fields. Then your users can disqualify.
Additionally you can add a Real-Time Workflow into the mix that prevents users from taking advantage of this loophole and qualifying without data. Have a check condition that checks if toggle is set to "disqualify." If yes, then next step is "Stop Workflow" with Status of "Canceled", and then a warning message that states "You cannot qualify this record if the toggle is set to disqualify."
Greetings of the day!
There are 2 factors to consider 1. Easy to implement & 2. robustness
Business Rule --> Simpler but it may not be robust for heavy work load with concurrency.
Real Time Workflow --> This one may be second best option you can consider considering above 2 parameters.
Business Applications communities