It is good practice to have some audit log of what uses do in the application. Some versions ago Microsoft introduced the Change Log to log data changes. How about logging an action execution?
One of the built in solutions in Business Central can be used to solve this. We now have the Activity Log (Table 710).
This video demonstrates how to implement the activity log pattern in Microsoft Dynamic NAV. The demonstration covers the following steps:
The Activity Log pattern tracks execution of activities. This is a Dynamics NAV specific implementation of the generic Audit Log pattern.
In general, integrating with external systems can be very challenging, due to the complexity of the situation – connectivity issues, asynchronous operations, user errors, etc. These challenges require sometimes re-trying several times, polling the external system, re-send/re-get data as all these activities can succeed but can very well fail.
Many years ago, when the Windows Client was till called the Role Tailored Client and was freshly released I blogged about how cues are handled in the menu.
Before NAV2016 each cues was automatically embedded in the menu, and grouped together if the system could find the same page in the Role Center.
Today at NAV TechDays 2015 in Antwerp, I attended a presentation by Nikola Kukrika, Ciprian Iordache, and Gary Winter, at which Ciprian presented a new design pattern based on a new feature in NAV 2016: Activity Log.
Since the release of Microsoft Dynamics NAV 2013, tracing user activity has become a bit more complicated than it used to be in earlier versions due to the fact that unlike previously, all user connections to SQL Server are now server connections. Which makes it more difficult to trace individual user activity.
So I had been upgrading a module from NAV 2013 to 2015. Selecting the module’s Role Center as default and running the Windows client made me wonder what I was missing. And then I saw the void.