NAV November ’16 Cumulative Updates

As we know, on the beginning of the month we get a new cumulative updates for Dynamics NAV. This month everything is the same as we already used to. We got Cumulative Updates for the following NAV releases:

As you can notice, we didn’t get Cumulative Update for NAV 2017. Maybe we will get it later, but I’m sure we will get the first one the next month.

nav_cu

On my first sight I didn’t see some features from NAV 2017 migrated to the older versions. Generally, there are standard platform and application hotfixes. Update your solution with the newest CU, but if you can – update your solution to the NAV 2017.

Advertisements

Problems with NAV on Upgraded Windows 10

In last few days, I’ve got a lot of comments about problems of NAV usage on Windows 10. Almost all or just all these problems are connected with situation when you have not installed Windows 10 from the scratch. These problems are on upgraded Windows 10 from some older version. I still not check about reasons for these problems, but they obviously exist.

I will try to check all these reasons in following days, but currently you can use this info to see how to solve these problems. Thanks to Francisco Bedolla for this article.

How to Upgrade NAV

Today, Microsoft has published new article about best practices and tips and tricks in upgrading process when you want to upgrade your solution to NAV2013R2 or NAV2015. After this first part about this topic, Microsoft already publish a second part with the same topic.The main reason why to read this article is because, the Classic Client is no longer supported by Microsoft. Now, it is the right time to make upgrade of your old NAV version.

Anyway, you can find awesome articles about this upgrade process here on MSDN Blog and part 2, as well. I recommend these articles.

Mainstream Support for NAV 2009 Ends

Mainstream support for all Microsoft Dynamics NAV 2009 versions ends January 13th, 2015. This is the last NAV version with the classic client. Of course, NAV 2009 also has RTC client, but a lot of companies use classic client. That means, Microsoft ends with classic client support.

Upgrade

Maybe, this is the right moment to think about upgrade to the newer NAV versions. In this situation I recommend NAV 2015. With the new Microsoft Dynamics policy, we have new cumulative updates every month, and if you use them, you will stay current in the future. That means, you will not have a need for new upgrade in following years, because you will always have the newest version. This will make a less of your investment in the future and less your users adapts to new versions – a lot of benefits.

Source: https://mbs.microsoft.com/customersource/northamerica/NAV/support/support-news/MainstreamSupportNAV2009

Merge-NAVApplicationObject -ModifiedPath?

I hope, you already know what is new PowerShell application merge tool in Microsoft Dynamics NAV 2015. The new application merge features include a few of PowerShell cmdlets, but now, I will write only about Merge-NAVApplicationObject.

This tool compares the changes that have been made between two sets of NAV application objects, and applies the difference to a third set of application objects. The result of merge are text files with the merged objects and text files with conflicts, where cmdlet could not merge them.

This cmdlet is as following:

Merge-NAVApplicationObject -ModifiedPath C:\Upgrade\MODIFIED -OriginalPath C:\Upgrade\ORIGINAL -ResultPath C:\Upgrade\RESULT -TargetPath C:\Upgrade\TARGET

To run this command, we have to determine what is ORIGINAL, MODIFIED, TARGET and RESULT.

ORIGINAL is the baseline of application merge.

TARGET is version of application that we want to apply the difference between the original and modified.

RESULT is finally version of merged objects with conflicts, as well.

But, what is a MODIFIED?

Can we set our customized database in MODIFIED (and new NAV version in TARGET) or we can use new version of NAV as MODIFIED (and our customized version as TARGET)?

We usually have a less differences between new version of NAV and ORIGINAL. When you make test with both combinations, you will see that merging when you use new NAV version as MODIFIED is two time faster in comparison when you set a your customization as MODIFIED.

But “two times” is in relation with minutes, not hours and it is not so important. Result is important. In my very complex example (a lot of customizations), results is almost the same. I have 1194 conflicts in one test and 1197 in other. That means, it is also not important.

But very important thing is that if you set NAV new version as MODIFIED, you can have problem with license in import objects process.

Because of that, you always have to use your customized solution as MODIFIED and the new NAV version as TARGET.