This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2013, including hotfixes and regulatory features that were released in previous cumulative updates.
This cumulative update replaces previously released cumulative updates. You should always install the latest cumulative update.
It may be necessary to update your license after implementing this hotfix to gain access to new objects included in this or a previous cumulative update (this only applies to customer licenses).
For a list of cumulative updates released for Microsoft Dynamics NAV 2013, see released cumulative updates for Microsoft Dynamics NAV 2013. For a complete list of all hotfixes released in cumulative updates for Microsoft Dynamics NAV 2013, view the following CustomerSource and PartnerSource pages:
CustomerSource
Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013
Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013
PartnerSource
Overview of Released Application Hotfixes for Microsoft Dynamics NAV 2013
Overview of Released Platform Hotfixes for Microsoft Dynamics NAV 2013
Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2013.
Important
We recommend that you contact your Microsoft Dynamics Partner before you install hotfixes or updates. It is important to verify that your environment is compatible with the hotfixes or updates being installed. A hotfix or update may cause interoperability issues with customizations and third-party products that work with your Microsoft Dynamics NAV solution.
Problems that are resolved in this cumulative update
The following problems are resolved in this cumulative update:
Local application hotfixes
CH - Switzerland
ID |
Title |
Functional area |
Changed objects |
233548 |
The Suggest Vendor Payments report also suggests credit memos in the Swiss version. |
Cash Management |
REP 393 |
ES - Spain
ID |
Title |
Functional area |
Changed objects |
230174 |
If you post a sales or purchase document for an EU customer or a vendor, the IDType is set to 06 and the ID is set to the customer or vendor number in the Spanish version. |
Finance |
COD 10750 PAG 472 PAG 473 TAB 114 TAB 124 TAB 325 TAB 36 TAB 38 TAB 5900 TAB 5994 |
230183 |
Non-taxable scenarios miss amount base on localization rules in the Spanish version. |
Finance |
COD 10750 PAG 472 PAG 473 TAB 114 TAB 124 TAB 325 TAB 36 TAB 38 TAB 5900 TAB 5994 |
230279 |
Invoice type F1 and F2 is missing in the sales and purchase credit memos in the Spanish version. |
Finance |
COD 10750 PAG 472 PAG 473 TAB 114 TAB 124 TAB 325 TAB 36 TAB 38 TAB 5900 TAB 5994 |
230929 |
If you create a sales credit memo and use VAT posting setup combinations with the EU Service field set and you do not set the SII interface, the export only exports in the Spanish version. |
Finance |
COD 10750 |
231217 |
An incorrect value is assigned on the ClaveRegimenEspecialOTrascendencia field in UE sales document in the Spanish version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
231587 |
Only invoice type F1, F2, and credit memo type R1 and R2 are supported in the Spanish version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
231631 |
If you post a purchase invoice with unrealized VAT and the Cash Regimen option is set to yes, all amounts are zero when you export to the SII interface in the Spanish version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
231635 |
If you have the Post Line Discount field set on the Sales & Receivables Setup page and then post a sales credit memo with multiple VAT rates and line discount, the export only contains one VAT rate in the Spanish version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
231733 |
The FechaRegContable field in the initial upload of purchase invoices is not filled correctly in the Spanish Version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
231749 |
If you post a sales credit memo of different type or blank, the information about the corrected invoice is missing in the Spanish version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
232519 |
The "Si el valor del campo BaseImponible es 0 se debe informar el campo ImporteTotal" error message is shown if you post document types F2 in the Spanish version. |
Finance |
COD 10750 |
232705 |
Sales and purchase documents with withholding taxes (IRPF) should not be included in SII XML files in the Spanish version. |
Finance |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
231201 |
Example XML message for registration when the counter party is not registered in the Spanish version. |
Sales |
COD 10750 COD 10752 PAG 21 PAG 26 PAG 427 TAB 18 TAB 289 TAB 36 TAB 38 |
IT - Italy
ID |
Title |
Functional area |
Changed objects |
231530 |
The DatiFattura file must always report the Sede node for all customers in the DTE file and all vendors in the DTR file in the Italian version. |
Finance |
COD 12182 |
231531 |
The format reported in the DatiFattura exported file is not correct in the Italian version. |
Finance |
COD 12182 |
232899 |
The tag of the DatiFattura purchase invoice file (DTR) reports TD10 even if the invoice is not an EU purchase invoice for goods in the Italian version. |
Finance |
COD 12182 |
NO - Norway
ID |
Title |
Functional area |
Changed objects |
232592 |
Document type is blank instead of the Payment field in the balancing line in the payment journal line when you import the return file for a SEPA payment in the Norwegian version. |
Cash Management |
COD 10635 |
Local regulatory features
ES - Spain
UK - United Kingdom
ID |
Title |
Functional area |
Changed objects |
232265 |
Payment terms reporting in the British version. |
Financial Management |
COD10525 COD113 COD90 MEN1030 PAG10556 PAG254 PAG256 PAG26 PAG29 PAG50 PAG51 REP10580 TAB10561 TAB10562 TAB23 TAB25 TAB38 TAB81 |