Announcing Microsoft Dynamics NAV 2013 R2 Cumulative Update 1

Announcing Microsoft Dynamics NAV 2013 R2 Cumulative Update 1

Rate This
  • Comments 16

We are happy to announce that the Cash Management team has shipped Microsoft Dynamics NAV 2013 R2 Cumulative Update 1. The cumulative update is available for download on PartnerSource/CustomerSource.

The cumulative update is an application update only. It mainly contains Cash Management features, such as:

  • UI for the Data Exchange Framework
  • Import of SEPA CAMT bank statements in W1 (all countries can use it) and in NL and BE in integration with existing localizations
  • SEPA Direct Debit in FR, IT, ES, BE, and CH in integration with existing localizations

As a new service, Microsoft Dynamics NAV 2013 R2 Cumulative Update 1 contains the "CU1Help" folder with selected topics for W1 and six country versions that have changed since Microsoft Dynamics NAV 2013 R2. The Help content is in English language only.

For more information about features in the cumulative update, see What’s New in Microsoft Dynamics 2013 R2 Cumulative Update 1, which is available from the download page or the country-specific What's New topics in the "CU1Help" folder.

To learn about known issues, of which the first has a prerequisite hotfix, see Release Notes for Microsoft Dynamics 2013 R2 Cumulative Update 1, which is available from the download page.

To follow installation steps and steps required to use the Data Exchange Framework and to update Help, see How to Update to Microsoft Dynamics 2013 R2 Cumulative Update 1, which is available from the download page. 

To help customers and partners get an overview of SEPA functionality released in different countries during the calendar year 2013, we have released the “SEPA Functionality in Microsoft Dynamics NAV” white paper on the Getting Ready site for Microsoft Dynamics NAV 2013 R2 on PartnerSource/CustomerSource.

Note: The product downloads, Help download, and links to supporting documents are presented in a separate section for Microsoft Dynamics NAV 2013 R2 Cumulative Update 1 on the download page on PartnerSource/CustomerSource.

Leave a Comment
  • Please add 8 and 1 and type the answer here:
  • Post
  • Thank you for this Cumulative Update 1.

    When I checked the object I still missing der objects changed by "NAV 2013 Update Rollup  6+7". Isn't a NAV 2013 R2 Cumulative Update the same than a NAV 2013 Update Rollup, is it?

    Is there any plan to get them also for NAV 2013 R2?

  • We were also waiting for the "2013R2 rollup update" this cumulatieve update confuses me.

  • Please notice that there is a difference between Cumulative Update and Update Rollup.

    This Cumulative Update is a small Application Feature Pack. The Update Rollup will soon be announced.

    please also notice that the Cumulative Update in mention will not be included in Update Rollup 1 for NAV 2013 R2. Update Rollup 2 for NAV 2013 R2 will include Cumulative Update 1 (available during December).

    /Martin

  • Honestly guys...this makes NO SENSE at all.. The number of rollups for NAV 2013 is crazy - and then you introduces a new set of updates called "Cumulative updates" ??? Does it REALLY matter that we get "update" today and not when the Rollup gets released ???

    Comon, we are facing difficulties to get paid for te REGULAR rollups..so stuff like this makes no sense at all !!!

  • @Palle: This is no different from how you receive regulatory features today. They come as a stand alone release and are then later enrolled to the monthly Update Rollup. I guess it is your own free choice if you want to wait for the next Update Rollup or wants to get started with these new features now. You will have to figure out what makes sense for your own situation, we just give different options for you to pick from.

  • @navteam: This IS confusing. Basically I don't care what the updates are called - it is an untenable situation when a NAV partner needs dedicated staff just to keep up to date on fscking "updates". How about releasing a solid product in the first place, for a change? I mean, I am not even asking for a workable GUI...

  • @Jens Glathe: I am not sure how to understand your comments? Is it like:

    1. I do not like that the NAV team improves the product on a regular basis?

    2. Or is it more like; I would like that the NAV team only releases improvements in a yearly or every second year?

    3. Or is it too confusing to differ between a Cumulative Update (which is like a feature pack) and an Update Rollup (which is a rollup of all hotfixes, RegF's and cumulative updates)?

    Or is your feedback to interpreted differently?

  • I love the monthly rollups. Only thing that bothers me now is the following:

    2013 R2 RollUp 1 has version 7.10.35701

    2013 R2 CumuUp 1 has version 7.10.35764

    CU1 was released before RU1 but has a higher version. CU1 "removes" features added in RU1.

    In what order do we merge these objects?

    It seems you need a RTM + RU1 + CU1 in this order. Because CUMULATIVE update 1 does not contain the ROLLUP 1 objects.

    And dont get me started on the 2013 SEPA objects! Which are based on RTM but also contains the bank export stuff released in RU6 or RU7.

  • @Martin Nielander: Relax, I'm not trying to insult you and I'm not out for a fight :) However, I AM frustrated with the product and with the release policy of the updates. What I would expect:

    1. Fixes: Real fixes of bugs, no new features or changing of the code base structure on the fly. All this in rollups, that'll be fine. What's not ok is when captions are reset to english because you've changed the W1 caption... this is a major pain for every user of localized versions, that'll be most of us NAV partners. Or you make major changes in (for example) CU 12. This is a real pain for partners with Add-Ons.

    2. Feature Updates: If it has to be... but then based on a easily to find source base, or it's a merge nightmare.

    The problem with these updates is that it is costing us real time (= money) with every little regression that happens due to code mismatch. I use a revision control system to keep track of it, but even with it it's a major PITA because of the release frequency and the little nasties in it (captions). Remember: we need to verify that our Add-Ons also work as expected with the new code, or it's support hell / no money earned.

    And yes, having so many fix releases does lead to poorer quality, as it seems. Just have a look at the echo from the release of NAV2013 R2, and the need to hold a "mythbusters" speech as a containment measure. Maybe a little more real-life user experience would help.

    with best regards

    Jens

  • Sebastiaan, Update Rollup 1 (UR1) was released before Critical Update 1 (CU1), hence the earlier build number. However, UR1 was announced later than CU1. That is all my fault, as I was out for a while during November, which caused a delay in the UR1 announcement. I apologize for the confusion this has caused. UR2, which will be released in December, will include the changes from CU1. For now you are correct, you should apply UR1 first, then CU1. /Susanne

  • @Jens: No worries, I was just trying to understand your feedback.

  • Might it be a bit confusing calling something NAV related CU1, as to most of us it means CodeUnit 1 not Critical Update 1.  I can only forsee confusion...

  • Guys,

    I'm getting an error after technical upgrade:

    The following SQL error was unexpected.

    INVALID COLUMN NAME 'Queue Folder Path', etc etc.

    it's all the final fields of the Marketing setup table.  What is the cause/solution for this?  Compiling all tables did not resolve the issue.

  • @S-GI-1: Please see if following the flow (starting from step 6) will help you:

    blogs.msdn.com/.../upgrade-toolkit-for-upgrading-data-from-microsoft-dynamics-nav-2009-r2-and-microsoft-dynamics-nav-2009-sp1-to-microsoft-dynamics-nav-2013-r2.aspx

    We'd seen this issue before, and it would normally be resolved either by recompiling the system tables or by restarting the server.

    Kind regards,

    Dmitry

  • Dimitry,

    No, those did not resolve the issue.  We followed the steps for 3 straight attempts at the upgrade and it still gives error.  Recompiling and restarting the service did not help either.

Page 1 of 2 (16 items) 12