Coffee Break: NAVDiag

In the previous two posts, Automation Part 1 and Part 2, we talked about how to easily bring PowerShell into NAV.

Based on the applicability and interest shown so far we wanted to continue on the previous thread and address some of the suggestions we received, as well as add some functionality. We called the result NAVDiag. This can be a tool that helps you simplify and speed up the troubleshooting, but above all - we hope this will create engagement around tooling possibilities and inspire for more suggestions.

In this edition we have added examples of how to read the license file and read the config file. Exporting license file is done using NAV cmdlet and as running NAV commandlets requires elevated permissions,  in order to run NAV cmdlets from this tool your NST account must be an admin account. In general, we are trying to avoid functionalities that require elevated permissions in these examples, as the point is simplicity and the ability to use this on a default configuration without any further installation or modifications needed. But after your feedback we thought this could be useful to have under a caution that running actions that invoke NAV cmdlets will fail unless NST user account has elevated permissions.

Another functionality we added is capturing repro steps when troubleshooting using Windows Steps Recorder. This is initiated using client side .net interoperability, so this functionality will not run (nor be present) on a WebClient (see limitations). The same would apply to collecting diagnostic details client side (can be used on Windows client only).  Collecting client-side data was one of the questions/suggestions we got and is something that we will come back to soon. For now, we would like to wrap up the functionalities that do not require any changes to default configuration.

So here it is:



The tool now allows you to collect diagnostics, the same diagnostics we presented in the last post, with added examples of reading the config file, the license file and Steps Recorder.

Record Steps action will allow user to record problem steps and save the output. This is basically just a call to the Windows built-in Steps Recorder function, but still useful to have as a part of the tool. Finally, the License File action will read the license file, provided NST account has elevated permissions.

There will be more coming up but if you find this useful and have further ideas about how this can be improved and used in your daily tasks, please let us know.



Comments (3)
  1. Mathias says:

    This is a great guide and a great inspiration! Thank you!

    but I was wondering if you could elaborate on how to get information about services running on remote machines, for example a NAS service running on a different server than the NST. I cannot find any documenation about the Microsoft.Dynamics.Nav.PowerShellRunner.dll…

  2. Peter Tijsma says:

    Hi Jasminka,

    I was wondering if you have plans to add an AddScript Command instead of only adding commands.
    I’m using PowerShell from NAV a lot (now using Waldo’s scripts), but most of the processing I’m doing is simply to first load a bunch of scripts and when those are loaded execute a command against them.

    Not sure if I’m clear, but otherwise let me know.


    1. @ Mathias and Peter
      Excellent ideas, and thank you for submitting those! Both sound like something that would be very useful indeed. Do allow us a bit time to plan and add features like these, and please keep the suggestions coming

Comments are closed.

Skip to main content