<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=523033&amp;fmt=gif">

Tracking Object changes in NAV

It’s become more and more important for companies to track when objects are changing in their NAV databases.  Fotolia_117120207_Subscription_Monthly_XXL-1.jpgWhether companies have developers on staff or work with a partner for NAV modifications it is important to have a solid software development process that includes the right documentation for changes and updates to the system. It’s especially important for firms thinking of doing an upgrade or re-implementation.  The longer an organization uses NAV the more likely they are to have modifications. With upgrades it can be difficult to tell if a modified object should move forward or not, especially if the object was not documented properly in the first place.  This can cause delays or unnecessary code being brought forward.  There are some pretty basic things companies can do to assist with tracking changes. These include:

  1. Tracking Change Requests. Create a way to track the change request. It can be an email string or a help desk ticket as long as change ties back to a request and approval.
  2. Document Code Changes. Always document the changes in the code, if possible make sure that code documentation ties back to the original request. Change documentation should happen in the documentation trigger of an object, next to where code was added, and in the version tag of the object itself.
  3. Export Original Objects. Always export a copy of the original object before changes as a fob and a text.
  4. Export Final Objects. After the changes are made and the object has been tested and signed off on, export a copy of the final object as a fob and a text. Make sure proof of testing and sign off is captured as well for later reference.
  5. Store Original and Final Objects together. Always store the before and objects together. This way the old and new objects can be compared using a simple text compare tool to identify changes.

Audit Trail tracks changes at the SQL database level, so it is able to track object changes where theNAV change track webinar link NAV Change Log cannot.  The NAV Change Log does not allow the selection of system tables through the user interface to turn on tracking at the object level.  The NAV Change Log will let show if someone changes data in a table, but not that someone added a field to the table.  The NAV Change Log will also not show any changes that are made through SQL. It can only show changes made through the user interface.


Audit Trail will track the user, date and time that an object changed. It does not show the lines of code that were changed and which application changed the object.  For example, if someone went into SQL and modified an object like the customer table, the fact that it was modified would show in the log.  The specific modifications should be captured through the software development processes.


Audit Trail will track insert, update, and delete events related to objects and then display the information in GRC Studio in the NAV Object Changes.  This report should be reviewed on a regular basis and can even be setup to automatically be e-mailed to someone for review and sign off. Additionally, the Fastpath Outlook plug -in will enable users to sign off from outlook and the sign off will be captured in a log.