Like any other code, AL code can be flawed and break during refactoring. To prevent manual testing, each time you make the smallest change in code, it is necessary to write Dynamics 365 Business Central AL automated tests. Dynamics 365 Business Central AL automated tests are pivotal to ensure that your code works correctly after refactoring or addition of new functionality.
One of the most popular blog posts I have written in recent years is this post on how the RelativePath and Query options for the Web.Contents() M function can be used to allow datasets that use web services as data sources to refresh successfully in the Power BI Service. It’s very frustrating when you write some complex M code in Power BI Desktop and find that your dataset can’t be refreshed after it has been published!
It’s been a while that I wrote on NAV and automated tests. In the meanwhile I have been teaching a lot all over Europe, and, yes, advocating test automation in NAV. And what did you do since my last post How-to: Run Standard Tests against Your Code? Did you dare and try? And did you also have the time/guts to continue with it? I know some that did.
I am working a web Service project with a customer and having trouble in communication because from NAV we actually do nothing related to web service publishing.
Let me try to explain the problem –
If a customer request you to publish a page as web services, for example, “Customer List” Page what we do.
1. We open Web Services page.
2. Add a New record, of Type Page and ID 22 and give a Service Name like cust.
3. Share the URL with the customer.
Have you ever felt that Dynamics NAV is sooo slow especially after having restarted the Server Tier?
Every time you are going to Demo Dynamics NAV to a customer or a group of potential new users, you always have to make excuses that Dynamics NAV is always slow just after having been restarted.
With our upgrade to NAV 2016 from NAV 2009 R2 many new things came available to us at The Learning Network, formerly known as Van Dijk Educatie. Technical improvements like the performance of the service tier, which was one of the major reasons for wanting to leave behind NAV 2009. But of course, next to a vast number of functional features, also the availability of PowerShell cmdlets, upgrade codeunits and test automation.