Problem in Cumulative Update 19 for Microsoft Dynamics NAV 2013 R2

Because of an inconvenient change of data schema in the application, the application bits are excluded from Cumulative Update 19 for Microsoft Dynamics NAV 2013 R2. A new release of CU 19 without application bits was released today, May 28. For more information, see Cumulative Update 19 for Microsoft Dynamics NAV 2013 R2 has been released.      

If you downloaded the initial release of CU 19 (released May 11), and you still want to implement it despite the problem in the application code, please read the following information. 


Cumulative Update 19 for Microsoft Dynamics NAV 2013 R2 has a problematic change that will affect your implementation of the cumulative update.

The problem is in table 114, Sales Cr. Memo Header, where the number of field 1300, Canceled, is changed to 1301. A typical partner development license does not allow field changes, so you will run into the problem when you try to import CU 19.



There is no good resolution at the moment (we are working on it), so here are two different ways to work around the problem.

Workaround 1: Rename the old field and merge the new field. Write code to copy values from the old field to the new field, as follows:

  1. Open table 114 for editing and rename the Canceled field to “Canceled 2”.
  2. Create a new object (for example a codeunit) in an allowed range.
  3. Create a variable named SalesCrMemoHeader with datatype Record and subtype Sales Cr.Memo Header.
  4. Copy/paste the following code:

    SalesCrMemoHeader.SETRANGE(“Canceled 2”,TRUE); SalesCrMemoHeader.MODIFYALL(Canceled,TRUE);

    SalesCrMemoHeader.MODIFYALL(“Canceled 2”,FALSE);

  5. Run the new object. All data will be transferred from the Canceled 2 field to the Canceled field.



You will not be able to remove the old field.

In table 112, Sales Invoice Header, field 1301, Canceled, is a FlowField that uses field 1301 in table 114 in its CalcFormula. Because table 112 is not part of CU 19, the CU will fail if you try to compile table 112 because it points to non-existing field 1300 in table 114.


Workaround 2: Import table 114 as a .fob file. (The partner development license does not allow deletion of an existing field if you import the table as a .txt file.)

  1. Save the data in custom fields.
  2. Import table 114 as a .fob file. (Note: This will remove the custom fields.)
  3. Re-apply any customizations that you may have lost.
  4. Move the data back.


Sorry for the inconvenience.

The Dynamics NAV team

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!