Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
Back in the day (I'm sure few of you remember) one would add validation script to buttons -- if the function returned true the button action continued else it would just stop.
All I can see is how to check the condition -- and flash the alert -- on form load while using an enable rule. I.e. onLoad vs onClick.
Am I missing something?
What you can do here - you can customize the command of the button, copy the handler that is being called and develop own function that do validation and call OOB handler if validation is passed. I did that for Close as Won/Close as Lost for Opportunity.
Thanks AB. Sounds dangerous. Not sure I know how to call a handler.
Here is the post that can help you - dynamics365blocks.wordpress.com/.../
Business Applications communities