Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
A recent requirement came up on a project to require specific fields when marking an Opportunity as Won. The reasoning for this request is that you want your sales team to be able to quickly enter their opportunities without having to fill out a bunch of required fields. However, you may also have specific fields that are needed upon closing the opportunity as Won, that you encourage your sales team to capture along the sales process.
At first, I thought that you could accomplish this by requiring fields in the last stage of the Business Process Flow. Nope, that’s not the case. Even if there are required fields in the BPF at any stage, users can go ahead and close the Opportunity as Won or Lost at any point.
Consider the Opportunity below. Notice how Contact, Est. Close Date, Est. Revenue, and Budget Amount aren’t required.
However, you want this data captured before someone can mark the Opportunity as won. You could invest in a developer and have them write a plugin to prevent save, but that would be costly.
The easy “no code” option is to use a Synchronous Workflow. Head over the Settings –> Processes to create your new workflow. Make sure to uncheck “Run this workflow in the background (recommended)” in order to make the workflow synchronous (or in other words, the Opportunity form won’t refresh until the workflow has run and completed). This is key, because we’ll add a step in the workflow that will prevent the save, if our fields aren’t populated.
Your workflow would need to run After the “Record status changes”, and it will only need three steps:
The overall workflow would look something like the following, along with the individual steps:
Now, when someone attempts to close an Opportunity as Won with those four fields above not populated, they’ll receive an error message as shown below. All of this was done without a single line of code, and should the business requirements change and warrant future modifications, you can easily hop back into the workflow and make those changes quickly.
If you’re looking to leverage Dynamics 365 to better monitor, track, and move through Opportunities, let us know! We’d be happy to discuss your existing environment and how we might be able to help.
Business Applications communities