Cumulative Update 10 for Microsoft Dynamics NAV 2013 R2 has been released

Cumulative Update 10 for Microsoft Dynamics NAV 2013 R2 has been released

Rate This
  • Comments 9

Cumulative update 10 includes all application and platform hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013 R2.

 The cumulative update includes hotfixes that apply to all countries and hotfixes specific to the following local versions:

  •   AU - Australia
  •   AT - Austria
  •   BE - Belgium
  •   CH – Switzerland
  •   CZ – Czech Republic
  •   DE - Germany
  •   DK - Denmark
  •   ES - Spain
  •   FI  - Finland
  •   FR - France
  •   IS - Iceland
  •   IT - Italy
  •   NA - North America
  •   NL - Netherlands
  •   NO - Norway
  •   NZ - New Zealand
  •   RU – Russia
  •   SE - Sweden
  •   UK - United Kingdom

License Versioning

Microsoft Dynamics NAV 2013 R2 Cumulative Update 10 introduces license key versioning to Microsoft Dynamics NAV. Observe the following specifications:

  • Microsoft Dynamics NAV 2013 R2 license keys will continue to be backward compatible with Microsoft Dynamics NAV 2013 instances.
  • Microsoft Dynamics NAV 2013 license keys cannot not be used with Microsoft Dynamics NAV 2013 R2 instances. Accordingly, newly issued Microsoft Dynamics NAV 2013 license keys will not work with Microsoft Dynamics NAV 2013 R2 CU10 (or later) instances.
  • Microsoft Dynamics NAV 2013 and Microsoft Dynamics NAV 2013 R2 license keys are not forward compatible with Microsoft Dynamics NAV 2015 instances.

 More details about license versioning will be made available in the October 2014 release of the Microsoft Dynamics Perpetual Licensing Guide.

Where to find cumulative update 10

You can download cumulative update 10 from KB 2984452 – Cumulative Update 10 for Microsoft Dynamics NAV 2013 R2 (Build 37563). We listed a different build number when this blog post published the first time, and we apologize for the resulting confusion. the correct build number is 37563.

For a full list of all hotfixes included in cumulative updates for Microsoft Dynamics NAV 2013 R2, see the following CustomerSource and PartnerSource pages:

CustomerSource:

     *  Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2

     *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2

PartnerSource

     *   Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013 R2

     *  Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013 R2

More Information

 For more information about cumulative updates for Microsoft Dynamics NAV 2013 R2, see Announcement of update rollups for Microsoft Dynamics NAV 2013 R2.

 

Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post
  • Hi,

    the actual build number appears to be 37563. Which is the right one?

    with best regards

    Jens

  • The fobs in the CU versions, are they compiled with the CU version build or with standard NAV build? It is a bit confusing when the developer klient doesn't warn me when I'm trying to import a newer build version.

    Correct me if I'm wrong but the text-"fobs" doesn't contain any build code so these are safe to import in version were the FinSQL.exe is of a lower build version then the "text build".

    But if the fobs are compiled in the same CU version as it is it could be a problem to import them into lower exe builds?

  • Hi all,

    Sorry for the confusion, but the correct build number is indeed 37563. The announcement has been updated accordingly.

  • @Capone: Everything we release in a CU is compiled and tested together. I am not sure what you mean by "CU version build" or "standard NAV build", in my world there is no difference between these two.

  • Hi Martin,

    ... but there are :) The question is: Can you import objects compiled with a higher build no. into a system that has a lower build no. with no adverse effects? I know that the opposite isn't always true. I had quite a hard time getting a NAV2013 system that was running on NAV2013r2 binaries updated to newer (NAV2013) objects. Even importing new tables fail when there are dependencies taht can't be resolved at import time. Reference: www.mibuso.com/.../viewtopic.php

    with best regards

    Jens

  • @Martin

    Back in the "old days" it was very common to do a technical upgrade to a newer version or build. The objects could be in version/build X but the client was in version/build Y.

    There has always been issues when you try to import fobs (not text) from a newer to an older build version. This problem doesn't happen with text files.

    My first question: The released fob files in the CU (Cumulative Update) are they compiled with the same build number or are they compiled with a client that has the same build no as the first released version of 2013 R2.

    If it is the later it would be easier to upgrade the application without having to upgrade the platform as well.

  • I just applied the update to current installation and none of the build numbers have been updated. Not on the NST and not in the clients.

    Not so strange that the build number doesn't change on the client since there is no new client exe file in the RTC folder.

    However if reinstall the entire installation it gets the correct build nos.

  • Czech version is included? I do not see it in download list... ???

  • @Capone: files in the CU is tested and compiled together (same build number). So nothing in a CU is compiled on an earlier version.

Page 1 of 1 (9 items)