I’d like to raise some attention on this topic, as this is quite important for partners that are supporting customers. In the old days, we received fobs and txt files with objects that only contained the changes for the TAX update. On top of that .. different TAX updates within one NAV release, were based on each other. So, the second update was based on the first and so on.
So what was the problem?
Well, I think we can all agree that there were sometimes quite a lot of quality-related issues with it. It was fairly easy to do it, because the number of objects was usually limited .. but a lot of partners have a lot of customers .. So doing it twice was out of the question. Now, there were times that it needed to be done a couple of times, because of .. uhm .. “undocumented features”.
As you know, now we have Cumulative Updates. And you should really work on your product and upgrade-organization that way, that it is “easy” to “upgrade” to the latest cumulative update. Definitely now because the TAX updates (which are quite important for most of the customers …) are included IN these cumulative updates.
My guess is that it’s not going to be possible anymore to just do the changes to comply with TAX regulations. You’ll have to upgrade to the latest CU.
No need to tell you more. Just read it on PartnerSource. Two things left to say though:
- It’s applicable for all Microsoft Supported Countries where Cumulative Updates exist.
- It’s applicable for versions Microsoft Dynamics NAV 2013 and higher.
My two cents
The new Merge-commandlets are going to be very useful for this. Only thing is .. You’ll have to work on your development guidelines and products that way, that it’s “always” easy to merge the new updates into you product/customerdb’s. Internally we have done this the past year-and-a-half .. with succes. An CU only costs us about 15 minutes of real merge-work .. the rest is automated.. .