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
Can anyone help provide information on how to do a simple upgrade codeunit so that table data is not lost during an extension upgrade, and provide an example of one? We are doing internal development, and are about to go live with our software. When we have our partner deploy our extension I will need to have a upgrade codeunit for them. Reading the page on microsofts site doesnt really help, and our partner just sent us that link.
Check this blog
Are you upgrading the extensions from V1 to V2, or are you worried about the data when you increase the version number of your extension? I did some trial and error on this topic few months back and it seems to me you have to worry about the data if you go from V1 to V2. When installing a new version of your v2 extension, the system will archive and restore the data without an upgrade codeunit if the table structure allows for the install. I will include few codeunits that have all the triggers available for install or upgrade, but the code is commented as it seemed completely redundant.
Business Applications communities