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
When running AL and C/SIDE side by side you always want to have your symbols up to date, this can be done by starting up finsql.exe with the parameter generatesymbolreference=yes as described here, but it’s also possible to generate symbols at compile time when using the Compile-NAVApplicationObject cmdlet.
For some weird reason the parameters regarding symbol generation were only added to finsql.exe and not to the PowerShell cmdlets (the place where I would expect them)
Luckily there’s a way to hack-in additional parameters to the Compile-NAVApplicationObject cmdlet by abusing the filter parameter as shown below:
This $filter variable can then be passed to the filter parameter of the Compile-NAVApplicationObject cmdlet, please be aware that those odd quotes are really!
This screenshot is taken from the Compile-ObjectsInNavContainer cmdlet in the NavContainerHelper but it’s also perfectly possible to use this in non Docker scenarios.
Thanks to Freddy Kristiansen for sharing this one!
Business Applications communities