This article applies to Microsoft Dynamics NAV 2015 for all countries and all language locales.
Overview
This cumulative update includes all hotfixes and regulatory features that have been released for Microsoft Dynamics NAV 2015, including hotfixes and regulatory features that were released in previous cumulative updates. Converting a Database in Help for Microsoft Dynamics NAV. 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 2015, see released cumulative updates for Microsoft Dynamics NAV 2015. Cumulative updates are intended for new and existing customers who are running Microsoft Dynamics NAV 2015. 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.
Note You must convert the database if you are upgrading to this cumulative update from a cumulative update earlier than cumulative update 9 (build 41779). For more information, seeProblems that are resolved in this cumulative update
The following problems are resolved in this cumulative update:
Platform hotfixes
ID |
Title |
---|---|
378900 |
The system makes the wrong selection when you select a different record. |
379057 |
The "&" character is not displayed on the page caption. |
378335 |
When you use the Quick Entry feature on sales order lines, the cursor jumps to the next tab. |
379513 |
The Set-NavServerUser and Set-NavSingleSignOnWithOffice365 sample scripts do not set the user object ID. |
378839 |
"The Company in Key does not exist. Identification fields and values: Company='testcompany', No.=." error message when you try to rename a company. |
379675 |
The SaveValues function only works randomly. |
Application hotfixes
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
378643 |
"Amount must be positive in Gen. Journal Line Journal Template..." error message when you post a check that includes a credit memo. |
Cash Management |
COD 11 |
379329 |
The Letter format is used as layout instead of A4 in the Adjust Exchange Rates report. |
Finance |
REP 104 |
378848 |
The total is incorrect in the Vendor - Balance to Date report. |
Finance |
n/a REP 121 REP 321 |
379388 |
"Applies-to Doc. No. must be equal to '' in Gen. Journal Line." error message if you use the Renumber Document Numbers function in the general journal and try to post the lines afterwards. |
Finance |
TAB 81 |
379224 |
When you revalue inventory that has costing method Average, unexpected cost amounts are calculated in the item ledger entries. |
Inventory |
COD 22 |
379282 |
An availability check warning is not raised when you change the requested delivery date on a sales line to an earlier date than when stock is available. |
Inventory |
COD 311 PAG 46 |
379335 |
"The field Item No. of table Purchase Price contains a value (XXX) that cannot be found in the related table (Item)." error message if you remove the vendor from the Purchase Prices header. |
Inventory |
REP 14902 PAG 7012 |
379633 |
Reservations are not canceled if they cause a date conflict when you change the sell-to customer number on the sales order. |
Inventory |
TAB 36 |
379350 |
The routing version is not based on the planning due date when you run the Calculate Regenerative Plan function on the Planning Worksheet page. |
Manufacturing |
COD 99000854 |
379441 |
The quantity for a component item that has reordering policy Lot-for-Lot is clubbed against a single reference order when you run the Calculate Regenerative Plan function. |
Manufacturing |
COD 99000854 |
379347 |
The To-Production Bin Code field is blank on the routing line of a planned production order that is created through a planning worksheet. |
Manufacturing |
COD 99000813 |
379324 |
Wrong values are calculated when you post a prepayment invoice in a foreign currency. |
Prepayments |
COD 442 COD 444 |
379477 |
"There is no Check Ledger Entry within the filter." error message when you use the Renumber Document Numbers function after printing checks and you try to void or issue a check. |
Purchase |
TAB 81 |
379342 |
The Rolled-up Assembly Cost field updates the Unit Price field on sales lines incorrectly when the ordered quantity is partially supplied by existing inventory and partially by an assembly order for the particular sales order. |
Sales |
TAB 904 |
379457 |
Invoices within the grace period are not correctly suggested in reminders. |
Sales |
COD 392 |
379408 |
When you add a line to a service contract, the service invoice is created incorrectly. |
Service |
COD 5944 |
379269 |
The credit limit warning is not raised in a service contract when you create a service line. |
Service |
COD 312 PAG 343 TAB 5965 |
379539 |
The service order is not created when you define a valid ship-to address in the contract. |
Service |
REP 6036 |
379469 |
"The Service Line already exists. Identification fields and values: Document Type=XX, Document No.=XX, Line No.=XX." error message when you insert a new service line. |
Service |
PAG 5905 PAG 5966 |
379012 |
Warehouse entries and item ledger entries do not balance. |
Warehouse |
COD 7302 |
379313 |
A sales unit of measure code with the same value in the Qty. of Base Unit of Measure per Unit field as the base unit of measure, such as 1 PCS., causes an incorrect allocation on a warehouse pick. |
Warehouse |
COD 7312 |
Local application hotfixes
AT - Austria
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379506 |
The cipher 067 value on the VAT Statement AT report is not filled correctly if the amount is negative in the Austrian version. |
VAT/Sales Tax/Intrastat |
REP 11110 |
CZ - Czech Republic
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379527 |
Correction of the check for bank account formats in the Czech version |
Cash Management |
COD 11706 REP 20 TAB 11731 |
379146 |
"Tariff No. must have a value in Sales Line Document Type=Invoice, Document No.=1011, Line No.=10000. It cannot be zero or empty." error message in the Czech version. |
Sales |
TAB 37 |
379526 |
The VAT Control report has issues when exporting to XML in the Czech version. |
VAT/Sales Tax/Intrastat |
PAG 31106 REP 790 TAB 179 XML 31100 |
DE - Germany
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379571 |
The Sales VAT Adv. Not. Acc. Proof report is not translated correctly in the Germany version. |
Finance |
REP 11009 |
ES - Spain
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379609 |
The <InstrPrty> tag under the <PmtInf> node and the <PmtTpInf>/<InstrPrty> node under the <DrctDbtTxInf> node are incorrect on the SEPA DD pain.008.001.02 XMLport in the Spanish version. |
Cash Management |
XML 1010 |
379628 |
The <Id>/<OrgId>/<BICOrBEI> structure under the <Cdtr> node are incorrect on the SEPA DD pain.008.001.02 XMLport in the Spanish version. |
Cash Management |
XML 1010 |
379423 |
The <PstlAdr> node is wrongly included under InitgPty in the SEPA DD pain.008.001.02 and SEPA CT pain.001.001.03 XMLPorts in the Spanish version. |
Cash Management |
XML 1000 XML 1010 |
379393 |
Wrong ledger entries are created after unapplying a payment that applies both the bill and the invoice, when the invoice has been posted before the bill in the Spanish version. |
Finance |
COD 12 |
FR - France
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379293 |
The wrong initial balance is printed on the Customer Detail Trial Balance and Vendor Detail Trial Balance reports if a payment tolerance is involved in the French version. |
Finance |
REP 10806 REP 10808 |
IT - Italy
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379276 |
If you pay a withholding-tax purchase invoice through a vendor bill list, the system assigns withholding taxes according to the Payment Date field on the Vendor Bill List page instead of on the Posted Vendor Bill Card page in the Italian version. |
Purchase |
COD 12101 |
378837 |
The Customer Bill List report does not show the right subtotal balance for partial payments when the payment is higher than the invoice and the stand-alone payments in the Italian version. |
Sales |
REP 12116 REP 12117 |
379369 |
If you run the Get Entries function from the EU Service Intrastat journal after you post an EU service invoice with different VAT prod. posting groups but with the same service tariff number, you receive wrong line amounts in the Italian version. |
VAT/Sales Tax/Intrastat |
REP 594 |
NL - Netherlands
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
379365 |
An incorrect VAT registration number is shown on the Intrastat Decl. report in the Dutch version. |
Finance |
REP 11413 |
379549 |
If you create an electronic VAT declaration, the figures for reduced tariff and other rates are in the wrong position in the Dutch version. |
VAT/Sales Tax/Intrastat |
REP 11403 |
RU - Russia
ID |
Title |
Functional area |
Changed objects |
---|---|---|---|
378987 |
The Customer - Reconciliation Act report shows an unexpected result in a scenario with two invoices and two payments in the Russian version. |
Finance |
REP 14910 REP 14911 |
379308 |
The VAT Sales Ledger report wrongly fills the СтПродБезНДС18 attribute in an .xml file when column 14 in an Excel file is empty and the report has two lines in the Russian version. |
Finance |
REP 12461 |
379275 |
Unexpected results in the assessed tax declaration are exported to Excel when you use exemption in the Russian version. |
Finance |
REP 14920 |
379493 |
The VAT Purchase Ledger report wrongly fills the СтоимПокупВ attribute in an .xml file and column 15 in an Excel file in the Russian version. |
Finance |
COD 12401 REP 12460 REP 12461 |
Resolution
How to obtain the Microsoft Dynamics NAV update files
This update is available for manual download and installation from the Microsoft Download Center.
Which hotfix package to download
This cumulative update has multiple hotfix packages. Select and download one of the following packages depending on the country version of your Microsoft Dynamics NAV 2015 database:
Country |
Hotfix package |
---|---|
AT - Austria |
Download the ATKB3166286 package |
AU - Australia |
Download the AUKB3166286 package |
BE - Belgium |
Download the BEKB3166286 package |
CH - Switzerland |
Download the CHKB3166286 package |
CZ- Czech |
Download the CZKB3166286 package |
DE - Germany |
Download the DEKB3166286 package |
DK - Denmark |
Download the DKKB3166286 package |
ES - Spain |
Download the ESKB3166286 package |
FI - Finland |
Download the FIKB3166286 package |
FR - France |
Download the FRKB3166286 package |
IS - Iceland |
Download the ISKB3166286 package |
IT - Italy |
Download the ITKB3166286 package |
NA - North America |
Download the NAKB3166286 package |
NL - Netherlands |
Download the NLKB3166286 package |
NO - Norway |
Download the NOKB3166286 package |
NZ - New Zealand |
Download the NZKB3166286 package |
RU - Russia |
Download the RUKB3166286 package |
SE - Sweden |
Download the SEKB3166286 package |
UK - United Kingdom |
Download the GBKB3166286 package |
All other countries |
Download the W1KB3166286 package |
How to install a Microsoft Dynamics NAV 2015 cumulative update
See How to install a Microsoft Dynamics NAV 2015 Cumulative Update.
Prerequisites
You must have Microsoft Dynamics NAV 2015 installed to apply this hotfix.
More Information
See more information about software update terminology and Microsoft Dynamics NAV 2015.
Upgrade Toolkit for Upgrading Data from Microsoft Dynamics NAV 2009 R2 or SP1 to Microsoft Dynamics NAV 2015
The cumulative update includes an upgrade toolkit for upgrading a Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1 database to Microsoft Dynamics NAV 2015. The upgrade toolkit includes several application objects in FOB files that simplify the upgrade process for those of you coming from Microsoft Dynamics NAV 2009 R2 or Microsoft Dynamics NAV 2009 SP1.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.