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
As publicly announced yesterday, the February 2019 Developer Preview for Dynamics 365 Business Central launches the first public version of the application where all the base code is converted from C/AL to AL.
If you open the old C/SIDE Development Environment, what you can immediately see is that you’ve only few system tables and system codeunits but no other application objects:
No standard tables, pages, reports, queries, codeunits, XMLports etc. :
Now all the base code is in a single AL extension called BaseApp (actually a monolithic app with about 6000 files):
If you want to create an extension for this new “absolutely alpha” application version and be able to have the symbols, ACTUALLY (and I repeat, actually!!!) you need to do two things:
Your app.json should be:
Now you will be able to have the symbols and (expecially) no strange errors during compilation:
All will be more stable for sure in the next releases (this is a preview ) but with these tricks in mind you will not loose too much time on troubleshooting strange errors from Visual Studio Code.
Business Applications communities