Everything about Dynamics 365 BC & NAV
Subscribe to my blog
We’re in an era where we are expected to deliver software more often and to deliver it faster, in other words, we’re expected to be agile. In order to be agile, we need continuous integration, continuous integration is a practice where members of a team integrate their work several times
Last week at directions Microsoft did a demo where they’ve shown the full solution running as an extension with only the system objects left in C/SIDE, that’s great, right? In this blog, I’ll share my thoughts on the subject and make you aware of the impact it has.
Just two weeks ago I released the initial version of my VS Code extension NAVBaaS Git at the Dutch Dynamics Community event, in case you missed it, you can catch up here. At first, I want to thank everyone that downloaded the extension and especially the people that gave me
I’m very happy to announce that my first Visual Studio Code extension called NAVBaaS Git has been released last Wednesday. The people who attended the session about Continuous Integration at the Dutch Dynamics Community event already had their first glimpse at the brand new extension and I really hope that
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.
It can be very handy to know which NAV Docker images are available on Microsoft’s public Docker repository, you can either do this the boring way by browsing this website (it will only show the 100? most recent tags) or the cool way by using (obviously) PowerShell.
With the release of the latest development preview most of the functions in the test libraries are marked as external, meaning they can be used for extension development!
With the current test framework and it’s limitations it can sometimes be hard to find a way to test your code, this gets even worse when external web services are called. I’ve seen a number of (bad) workarounds in the last few months varying from calling a nonexistent endpoint to
With AL you can already create test codeunits, write test functions but you have to use your own libraries because all functions in the standard libraries are not marked as external.. After reporting an issue on GitHub Microsoft confirmed they’ll be marked as external in the January update! In my
The time has come, we can finally run multiple NAV versions, cu’s and localization’s side by side with Docker, but how do we actually move our old and dusty c/side development environment to a modern place?
In the ideal world you have a nightly build, creating your entire solution from scratch, running all the automated tests that come with standard NAV and so on. During business hours you basically want the same thing but a lot faster, you want to have feedback about your modifications as
Automating your automated tests is just as important as creating and maintaining them, you want to be able to run your tests at least once a day and ideally multiple times a day or even after every check-in. All we have to invoke these automated tests is PowerShell but there’s
This is the first part of Automated testing with Permissions, in this post I’ll visualize and explain the way it’s described on msdn and in part two I’ll go for a more practical approach which will support permissions per test function and partial execution of code with a permission set.
Here’s another suggestion for the automated testing framework: a select function on a TestPage object. In some cases you might face a (runmodal) page where a user has to select one or more records and based on that selection an action is performed, right now it’s not possible (correct me
So today a colleague referred me to this page on MSDN where it states the following about the ID: If left unassigned the notification will be assigned an ID when the SEND method is called. For more information, see SEND Function (Notification). So this sounds like giving your own unique ID
Since C/AL unit tests run in a client session GUIALLOWED will always be TRUE, if code behaves differently in case of GUIALLOWED = FALSE it’s not possible to actually test that code. Especially when testing web services it would be great if you could just disable the UI in a test
Dynamic visibility of fields and page actions behave different in the web client, make sure you are aware of the following limitations. Fields: – Code in the visibility property will not work – Using a variable to determine visibility only works once – On a group this works as expected, workaround