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, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
Some of our customers require an purchase number when they receive an order from us. So on the accounts we have an field which contains yes or no, when somebody created an quote this yes/no is also filled on on the form of the quote. If the value is yes another field is enabled where we can fill in the purchase number of the customer.
Now the problem we are facing: The backoffice regularly forgets to fill in the value on the quote. So our project department needs to e-mail the back-office for this number which costs time. Can we create a check when somebody hits the button 'close as won' if the value of the purchase number (when it's required) is filled in? If not warn them to fill in the form or else the project department will get back to them eventually?
Hi Jos. I would never touch the OOTB ribbon buttons. I think you have several customization options for this:
- Make the field Business Required
- Use a Business Rule with a Recommendation
- Use Java Script to present a custom message if the field is empty
On top of these all, remember that technology should not be used to fix a people problem. Train, train and train your users.
Business Applications communities