Every developer needs to debug every now and then.
But it becomes a challenge when you didn’t wrote every line of code.
Maybe an addon will case the problem.
Default NAV or a CU update can also be the reason.
Or the combination of these.
So where do you begin? First you start debugging and break just before you press the function that causes the problem.
Then you follow every line of code in the debugger. Jump from one codeunit to another. Very time consuming.
2 days ago Plataan and Microsoft has published another “How Do I” video of me.
Actually this video was already published 2 months ago but with a different title.
First the title was “How Do I: Use The New Development Environment in Microsoft Dynamics NAV 2016”.
But I have to admit Microsoft didn’t gave us a new Development Environment. They improved the existing one with new features and a couple of enhancements.
So it sounds logic that the title is now “How Do I: Benefit from Using The CAL Coding Enhancements in
Microsoft Dynamics NAV 2016”.
Every now and then you need a selection of records from a list page. To get the selection you need to add a global function like this:
PROCEDURE GetSelectionFilter@50000(VAR SalesShipmentHeader@50001 : Record 110);
Wouldn’t it be great if we can directly call for example PostedSalesShipments.GETSELECTIONFILTER(SalesShipmentHeader) by default?
Last Friday Plataan and Microsoft has published my next “How Do I” video.
In this video I show you how you can ask and use filters with the new FilterPageBuilder datatype in Microsoft Dynamics NAV 2016.
As I have warned you on my previous post, there was an issue where the OnAfterValidate Event wasn’t fired as expected.
Yesterday Microsoft has released CU5 of NAV2016 with a platform hotfix special for this behavior as you can see.