It is assumed the reader has in-depth knowledge of NAV development and can easily adapt the example shown below. With some experimentation, I found the solution. I searched Mibuso and Freddy’s blog and found client-side add-ins for a NAV Timer to be added to Page objects, but I didn’t see an example for a timer to be started in a single instance codeunit designed to be started by the NAV 2013 servicetier. I assumed without too much verification that the NAV Timer DLL was still using COM Automation and had not been upgraded to DotNet technology. Recently, the same need arose for NAV 2013, but because of the incompatibility between the COM Automation and the new 64-bit servicetier, I needed the DotNet equivalent. Thereafter, as long as the NAS was running, the timer would fire the event trigger using the specified interval. Within that codeunit, the NAV Timer would be started. For such a situation, I’d add code to the NASHandler function in Codeunit 1 ApplicationManagement … when the NAS service was added to Windows, it would be added with the parameter that would be hard-coded in CU1 to start a single instance codeunit.
The old Navision Application Server was the Classic Client without the GUI interface. For such cases, I would use a single instance codeunit and the NAV Timer (old-style COM automation technology).
There has been a time or two in the past (on older Microsoft Dynamics NAV versions and the old Navision Application Server) when I needed an automated process that would execute faster than the minimum one minute duration afforded to me by the Job Queue.
0 kommentar(er)
