Customizing Dynamics NAV
Discover different ways to customize the application to give you and your colleagues access to the features, functionality, and data that you need most.
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 and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I have been blogging a few times about the Diagnostic Descriptors we get when enabling code analysis. Well – yet again, we have new ones. But I’m not going to keep updating these rulesets, as Microsoft is now doing that on docs. So let me give you one more overview, and the resources to the pages on docs per analyzer.
Here we go….
For AppSourceCop, it was already known for a while, but now the cop is going to make sure you have a translation file when creating an app for AppSource. On top of that, also quite a good one, it makes sure you don’t forget the data classification (cfr. GDPR in Europe)
Also new stuff in the CodeCop (the generic analyzer which you should always enable):
The “PerTenantExtensionCop” analyzes as if you are writing a one-off customization for a customer in the cloud – so different rules apply.
Last but not least: the UICop to check the UI if UI guidelines are met.
Business Applications communities