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
So here's what happened:
What you may NOT have known, was that in certain instances, CRM has it own versions of those events.
The bug in the Export process was caused by me selecting the first instance for a specific event from entity. In some cases, that first event was "internal." I had a secondary check to only export user-created events which means that for certain cases, the utility totally skipped the OnLoad and OnSave events for some entities.
That has been corrected in this release ( 1.5.3 ).
You may find it on my free utilities page:
Business Applications communities