New Dynamics NAV August 2016 Cumulative Updates

Currently Microsoft hasn’t yet published that new Cumulative Updates are already published on their blog. But they already published Cumulative Updates for NAV 2015, NAV 2013 R2 and NAV 2013 in Friday. And, they have just published CU for NAV 2016 today.


You can download all these Cumulative Updates from the following links:

There are a lot of interesting Platform and Application hotfixes and local hotfixes as well and you just need to download and test them. I’ve just noticed them and I need to check all of these.

July 2016 NAV Cumulative Updates

Yesterday (July 5th) new NAV Cumulative Updates have been released. As usually in expectation of new NAV version, Microsoft published updates for the last four NAV versions:

You can download them for the previous links. If you are thinking if this is the right moment for your upgrade to the last version and the last Cumulative Update, the answer is YES. Very soon we will get the newest very impressive NAV version and this will be the first step in preparation for using the newest NAV version.


As usually, NAV 2016 has the most of hotfixes, both platform and application, NAV 2015 slightly less and for the other two versions, just few of them. You can also find some local application hotfixes.


June 2016 CUs for NAV have been released

Today, Microsoft has published new Cumulative Updates:

Generally, NAV 2016 has pretty more Platform Hotfixes than other three versions (they have only few of them). About Application Hotfixes, the last two version have most of all improvement.

Almost all Hotfixes, both Platform and Application are just improving some issues in system. If we wait something new, I think we will wait until new version will be published. In any case, I suggest to install the most recent cumulative update for your NAV version. And still better, upgrade your NAV to the freshest NAV version :). You will not make mistake.


May 2016 Cumulative Updates for NAV 2016, 2015, 2013R2, 2013

Yesterday, Microsoft has been published the newest Cumulative Updates for Microsoft Dynamics NAV 2016, NAV 2013R2 and NAV 2013. Today morning, Microsoft has published Cumulative Update for Microsoft Dynamics NAV 2015 as well.

There are the all Cumulative Updates based on versions:

There are not so many Platform hotfixes and more Application hotfixes for almost all business area. Newer versions as usually have more hotfixes.


As usually, these cumulative updates replace previously released cumulative updates.

April 2016 CU’s for Dynamics NAV

Few days ago, Microsoft has been published new Cumulative Updates for Microsoft Dynamics NAV 2016, 2015, 2013R2 and 2013. This time, there were only few platform hotfixes (four for NAV 2016 and two per all other versions). They also include some application hotfixes and regulatory features that have been released for these NAV versions:

  • NAV 2016 – Cumulative Update 6 (Build 45480)
  • NAV 2015 – Cumulative Update 18 (Build 45483)
  • NAV 2013R2 – Cumulative Update 30 (Build 45478)
  • NAV 2013 – Cumulative Update 37 (Build 45477)


You can check all hotfixes and download these cumulative updates on the following links:

What about FEFO and Costing

After my the last article, I’ve got comments about FEFO. First, thanks for reading my blog :), and then yes, it deserves to write a few sentences about it, because it is very useful feature in NAV.

But first, what actually FEFO means? It is First-Expired-First-Out method. What is the first we have to notice about it? FEFO is a picking method, but it is not a costing method. This method is important for a lot of very specific industries (pharmacy, food…), but it is just one specific way how to configure your location.


If you want to use FEFO, your items have to have configured a serial or/and lot numbers. In additional on each item tracking code setup, the SN-Specific Warehouse Tracking field or the Lot-Specific Warehouse Tracking field must be selected. And now, we can conclude that FEFO actually uses Specific Costing Method. It is FEFO, but it is nothing more then Specific method. Everything is the same as in all other Specific Method types, but when you select FEFO on your location, system will take care about picking order using expiration date.


You can find more about FEFO on MSDN here or in Mark Brummel Application Design book.

Costing in NAV – Inventory Posting

Costing methods usually differ in the way that they value inventory decreases. But, regardless of what costing type you use, all of them have minimum one common thing. When the quantity on inventory is zero, the inventory value must also be zero. The next common thing is way of the posting all incoming and outgoing entries. This posting results entries as quantity and as value. Quantity posting describes the change in quantity on inventory and this transaction is stored in Item Ledger Entries. Value posting describes the change in inventory value and this transaction is stored in Value Entries. Each entry in Value Entries table is linked with entry in the Item Ledger Entries table. More entries in the Value Entries table can be applied with the same entry in the Item Ledger Entry.

Each Item ledger entry is applied against each other. All these applications between incoming and outgoing quantities in the Item Ledger Entries are stored in the Item Application Entry table as links between inventory increase and inventory decrease in an Item Ledger Entry. NAV records the entry number of the Item Ledger Entry corresponding to the inventory increase in the Inbound Item Entry No. field and the entry number of the Item Ledger Entry corresponding to the inventory decrease in the Outbound Item Entry No. field. The program also reduces the Remaining Quantity fields in the corresponding item ledger entries by the applied quantity.

Based on the Inventory Posting Setup, system will post all these entries to the General Ledger Entries.