![microsoft dynamics nav 2009 user manual pdf microsoft dynamics nav 2009 user manual pdf](https://i.ytimg.com/vi/7p1BmVgGkxQ/maxresdefault.jpg)
End-users generally do not have access to modify these tables, and if they do (i.e. Ledger Entry, Vendor Ledger Entry, et cetera). Ledger data is the final table type to log (GL Entry, Cust. With these types of tables, we generally log specific values or ensure that the business processes used in the environment do not adversely affect the performance of the environment. Sales Header, Sales Line, Service Header, Service Line, et cetera) are continually being inserted into, updated, and then deleted in the system as a business process flow is executed. Transactional data is another story and generally, must be handled on a case-by-case basis because of the potential impact on your systems performance. We’ll explore this in a bit – why transaction volume matters to change log and how it impacts your system and performance. Customer, Vendor, Item, Resource, G/L Account, Dimension, Dimension Value, et cetera) as the volume of data changes should be minimal.
![microsoft dynamics nav 2009 user manual pdf microsoft dynamics nav 2009 user manual pdf](https://image.slidesharecdn.com/07fad401-0d5d-4c24-87f0-834dbe806445-160702082806/95/microsoft-dynamics-nav-2016-a-users-guide-3-638.jpg)
It’s generally a safe rule to log All Fields on master data tables (i.e. Master data is a common set of data that end-users log, and we generally recommend to do this type of setup to track changes made by end-users that could impact a business process flow within the system. In the case of a delete event, the system logs all fields as the All Fields value was setup in the Change Log Setup (Table) List page. In this example, the system has been setup to log the Payment Terms table with specific values, with the Some Fields setup, when inserting (creating) or modifying (updating) data. With change log activated, it still requires end-user setup to specify what tables are logged and what type of events are logged in the system. When opening the page, it allows for the end-user to enable the change log system by checking the “Change Log Activated” value in the system.įigure 1 – Change Log Setup in Microsoft Dynamics NAV 2009 R2 The change log system up to NAV 2009 R2 (pre-NAV 2013) is exposed to the end-user in Administration > Application Setup > IT Administration > General Setup > Change Log Setup (Task). In order to understand how this change can impact you and your users, we need to start with where you are possibly coming from (upgrading from a pre-NAV 2013 environment or below). There is basically two different (stock) change log systems that are now in the RTC: the pre-NAV 2013 change log (Classic/RTC) and the NAV 2013+ change log system.
![microsoft dynamics nav 2009 user manual pdf microsoft dynamics nav 2009 user manual pdf](http://thinkaboutit.be/wp-content/uploads/2016/12/r1.jpg)
How does Microsoft Dynamics NAV change log work?Īs with any product, improvements to base functionality occurs with most major releases, and change log had been an overlooked feature for some time. With Microsoft Dynamics NAV 2013, the system was changed in a subtle manner that had adversely impacted some of our clients and allowed me to take some time to dig into the details of the new system and what can be changed. 3.01.A was the first version that I worked with and it has been generally a valuable and sometimes overlooked (and misused) tool for our clients. The change log functionality in Microsoft Dynamics NAV has existed within the product since the old “Navision” days.