Problem in Cumulative Update 19 for Microsoft Dynamics NAV 2013 R2

Problem

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.

Resolution

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. See the following code snippet as an example.

SalesCrMemoHeader.SETRANGE("Canceled 2",TRUE);

SalesCrMemoHeader.MODIFYALL(Canceled,TRUE);

SalesCrMemoHeader.MODIFYALL("Canceled 2",FALSE);

Where “Canceled 2” is the renamed field.

Note:

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.

Next Step

There will be a hotfix available to resolve this issue soon. We will link to the hotfix from the current KB articles and blog posts, and we will create a new announcement when it is ready.

Sorry for the inconvenience.

The Dynamics NAV team