This article applies to Microsoft Dynamics 365 Business Central 2020 Release Wave 1 for all countries and all language locales.
Overview
This update replaces previously released updates. You should always install the latest update.
It may be necessary to update your license after you install this hotfix to gain access to new objects that are included in this or a previous update. (This only applies to customer licenses.)
For a list of updates that were released for Microsoft Dynamics 365 Business Central 2019 Release Wave 2, see released updates for Microsoft Dynamics 365 Business Central 2020 Release Wave 1. Updates are intended for new and existing customers who are running Microsoft Dynamics Released Updates for Microsoft Dynamics 365 Business Central 2020 Release Wave 1.
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 that will be installed. A hotfix or update may cause interoperability issues with customizations and third-party products that work together with your Microsoft Dynamics 365 Business Central solution.
Problems that are resolved in this update
The following problems are resolved in this update:
Release note
| ID | Title | Functional Area |
|---|---|---|
| 369662 | “Failed to acquire an access token" error message when you try to setup any Oauth2 integration. | Integration |
Workaround
- Go to nuget.org and download the required package by clicking "Download package": https://www.nuget.org/packages/Microsoft.Identity.Client/4.14.0.
- Extract the contents.
- Copy the contents from .\microsoft.identity.client.4.14.0\lib\net45\* to the NST binaries location.
- Restart the NST.
Platform hotfixes
| ID | Title |
|---|---|
| 365943 | Partner licenses do not grant access for device users. |
| 366255 | Improve the upgrade step to ensure that primary keys for companion tables are correct. |
| 360043 | The Role ID field is truncated when you import XML permission sets. |
| 365996 | The ShowAsTree property on a TreeView page does not work if the first field is not visible. |
| 368795 | When you change the selected row in a list, the page might scroll unexpectedly. |
Application hotfixes
| ID | Title | Functional Area |
|---|---|---|
| 368262 | The security filter is not working as expected after you deploy hotfixes. | Administration |
| 366225 | "The Credit Transfer Entry already exists. Identification fields and values: Credit Transfer Register No.='X',Entry No.='Y'" error message displays when you export the electronical payment file. | Cash Management |
| 364194 | When you post a new prepayment invoice after using the VAT Rate Change function, an incorrect VAT amount is registered for the prepayment invoice. | Finance |
| 364425 | After a VAT rate change, a VAT entry from a sales order with prepayments displays the new VAT Product Posting Group table, but the VAT amount is incorrect. | Finance |
| 365394 | Setting the No. Series Lines table to Allow Gaps in No. Series automatically inserts an extra digit in the Last No. Used field results in an incorrect update to the data. | Finance |
| 366966 | The Customer No. field is displayed in the sales history FactBox while the Vendor No. field is not displayed in the purchase history in documents, such as orders. | Finance |
| 367124 | The customer name should not be updated or replaced when there is no name associated with the VAT Registration No. field. | Finance |
| 367299 | In vendor ledger entries, it is possible to change the value in the Exported to Payment File field from false to true manually. | Finance |
| 368252 | After the VAT Rate Change, a VAT entry from a prepayment credit memo displays the new VAT Product Posting Group table, but the correct VAT amount that is calculated based on the old VAT Product Posting Group table. | Finance |
| 368608 | Numbering in the purchase credit memo behaves differently than in the purchase invoice. | Finance |
| 368884 | The Inbound Transfer of an average cost item is revalued, thus contributes to its own cost indirectly. | Finance |
| 369828 | The account schedules no longer successfully update Excel Template files by using the Export to Excel function. | Finance |
| 365815 | Unreal gain and unreal loss are not posted correctly. | Finance |
| 364722 | When you deal with a service order and transfer by using the order planning and the Reserve option, the Reservation status is set to tracking instead of reservation. | Inventory |
| 365381 | "The following C/AL functions are limited during write transactions because one or more tables will be locked" error message displays when you select an assembly item on a sales order. | Inventory |
| 366904 | Changed receipt date on an already shipped transfer order line is not reflected on the record, which causes an inaccurate receipt date information on the Available - Transfer Lines page. | Inventory |
| 367382 | The Outbound Transfer is not cost adjusted while the Inbound Transfer, which is split into several entries due to multiple cost relations, is a correctly cost adjusted FIFO item. | Inventory |
| 368548 | The transfer order variant code is cleared out if you change the Direct Transfer flag. | Inventory |
| 365390 | The assembly order is not created when an assemble-to-order item is pulled in via the Select Items option on a sales order. | Inventory |
| 365038 | Bin code is not transferred to the sales invoice created from the job planning line. | Jobs |
| 366066 | Lines with the Type = Text setting in Jobs Planning lines already invoiced can be changed to other type and invoiced again. | Jobs |
| 364326 | When you open the Routing page, the Prod. Order Line Bin Code field is updated with the bin code from the work center instead of maintaining the bin code from the header. | Manufacturing |
| 364820 | The Allocated Time field in the Prod. Order Capacity report does need to be consistent with the Needed Time field after you post the negative Run Time field. | Manufacturing |
| 365635 | The Segment Description field is not populated in the opportunity card. | Marketing |
| 364711 | "Quantity Received must be equal to '0'" error message displays after you post a purchase order where the Blanket Order Line No. field is blank even if the Blanket Order No. field is filled. | Purchase |
| 364920 | "Select a dimension value code for the dimension code customer group for Item : 1000, Create PO from SO" error message displays when a dimension used in the Requisition line. | Purchase |
| 365286 | When you deal with the requisition worksheet and set the Print Order option to yes, only the order related to the last worksheet line is printed. | Purchase |
| 363058 | The recurring purchase lines do not work properly when a currency code is defined. | Purchase |
| 363906 | Over-Receipt tolerance is not working when the Receive field is blank in the purchase order. | Purchase |
| 364994 | The Customer/Item Sales report automatically cancels if no Customer Ledger entries are present. | Sales |
| 365014 | Using Available to Promise (ATP) leads to incorrect earliest shipment date when you deal with sales orders and production orders. | Sales |
| 365188 | An unexpected unit price in the Price List report for an item without specific sales price list lines. | Sales |
| 365580 | "The record in table Sales Line already exists. Identification fields and values: Document Type='Order',Document No.='X',Line No.='X'" error message displays when you convert a sales quote in a sales order with the recurring sales lines defined. | Sales |
| 365628 | Too many modifications of requisition lines. | Sales |
| 366379 | The sales quote is not archived if you convert it into a sales invoice and you set the Archive Quote field to True in the Sales & Receivables Setup. | Sales |
| 366892 | The Qty. to Receive value entered on a line in a purchase order is not saved in the Web client when you tab out of the field. | Sales |
| 366939 | The Costs and Profit fields in the customer card is incorrectly reflected for resource in a service order. | Sales |
| 365495 | When you deal with the special price and line discount, the sales return order gets unit price updated while changing quantity, but the discount keeps old percentage. | Sales |
| 367137 | The Recipient Bank Account field should be visible and editable on the Customer Ledger Entry page. | Sales |
| 364320 | The total available quantity with the specific lot reservations and warehouse shipments/picks are not correct. | Warehouse |
| 365391 | "Lot No. xxx is not available on inventory or it has already been reserved for another document." Error message displays when you register a pick. | Warehouse |
Local application hotfixes
APAC
| ID | Title | Functional Area |
|---|---|---|
| 364447 | The job ledger entries are not created when you post a sales invoice created from the job planning line in the APAC version. | Jobs |
AT - Austria
| ID | Title | Functional Area |
|---|---|---|
| 366250 | New changes are in the VAT statement on July 1st, 2020 in the Austrian version. | Finance |
BE - Belgium
| ID | Title | Functional Area |
|---|---|---|
| 368203 | Incorrect statement amounts in the CODA Statement Line in the Belgian version. | Finance |
| 364447 | The job ledger entries are not created when you post a sales invoice created from the job planning line in the Belgian version. | Jobs |
CZ - Czech
| ID | Title | Functional Area |
|---|---|---|
| 364447 | The job ledger entries are not created when you post a sales invoice created from the job planning line in the Czech version. | Jobs |
| 365003 | Error message displays when you try to create an advance letter in the Czech version. | Sales |
DK-Denmark
| ID | Title | Functional Area |
|---|---|---|
| 366715 | Information from the Sell-to Contact No. field is not well retrieved in the sales invoice when you have a Contact No. field with the same Customer No. field of the sales invoice but related with other Customer No. fields in the Danish version. | Sales |
ES - Spain
| ID | Title | Functional Area |
|---|---|---|
| 363340 | "Bill XXX cannot be applied since it is included in a posted bill group" error message displays if you try to apply a bill already included in a posted bill group into a credit memo in the Spanish version. | Finance |
| 368891 | It is not possible to change the payment method in customer and vender ledger entries even if the document is not linked to the Cartera module in the Spanish version. | Sales |
IT - Italy
| ID | Title | Functional Area |
|---|---|---|
| 366837 | If you set the VAT period as Quarter, the previous Period Input VAT value is not included in the Periodic VAT Payment Communication report in the Italian version. | Finance |
| 366841 | On posting a payment for two open vendor ledger entries created from one invoice, incorrect VAT entries are created in the Italian version. | Finance |
| 365069 | If a sales invoice is issued for a customer classified as an individual person, the XML file of the invoice is not correct in the Italian version. | Finance |
| 364608 | An error message about PrezzoTotale calculation displays when the E-invoicing is not validated in the Italian version. | Sales |
MX - Mexico
| ID | Title | Functional Area |
|---|---|---|
| 365830 | The XML file for electronic invoicing is missing attributes, which causes infringement to SAT fiscal laws in the Mexican version. | Administration |
| 367157 | When a digitally signed invoice has one or more related credit memos, the code does not display the digital signature ID of the related invoices while you download the XML file in the Mexican version. | Sales |
NA - North America
| ID | Title | Functional Area |
|---|---|---|
| 367158 | Error message displays in the Drop Shipment report when the Item Description field has more than 30 characters in the North American version. | Administration |
| 367481 | The DIOT report is now working correctly in the North American version. | Finance |
| 367615 | The Use Stockkeeping Unit option is missing from the Purchase Advice page in the North American version. | Purchase |
UK - United Kingdom
| ID | Title | Functional Area |
|---|---|---|
| 365639 | The <ContactName> node is exported without data if you export the EC Sales List report in the XML file in the British version. | Finance |
Local regulatory features
NL - Netherlands
| ID | Title | Functional Area |
|---|---|---|
| 367107 | It is possible to see the XML request of the ICP declaration before submission in the Dutch version. | Financial Management |
| 365968 | The SEPA Credit Transfer payment export should work without using the Telebanking module in the Dutch version. | Financial Management |
NO - Norway
| ID | Title | Functional Area |
|---|---|---|
| 361299 | Improve the SAF-T performance in the Norwegian version. | Financial Management |
Resolution
How to obtain the Microsoft Dynamics 365 Business Central 2020 Release Wave 1 files
This update is available for manual download and installation from the Microsoft Download Center.
Update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1
Which hotfix package to download
This update has multiple hotfix packages. Select and download one of the following packages depending on the country version of your Microsoft Dynamics 365 Business Central 2020 database:
| Country | Hotfix package |
|---|---|
| AT - Austria | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 AT package |
| AU - Australia | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 AU package |
| BE - Belgium | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 BE package |
| CH - Switzerland | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 CH package |
| CZ- Czech | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 CZ package |
| DE - Germany | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 DE package |
| DK - Denmark | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 DK package |
| ES - Spain | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 ES package |
| FI - Finland | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 FI package |
| FR - France | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 FR package |
| IS - Iceland | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 IS package |
| IT - Italy | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 IT package |
| NA - North America | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 NA package |
| NL - Netherlands | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 NL package |
| NO - Norway | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 NO package |
| NZ - New Zealand | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 NZ package |
| RU - Russia | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 RU package |
| SE - Sweden | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 SE package |
| UK - United Kingdom | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 UK package |
| All other countries | Download update 16.5 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 W1 package |
How to install a Microsoft Dynamics 365 Business Central on-premises 2020 Release Wave 1 update
See How to install a Microsoft Dynamics 365 Business Central 2020 Release Wave 1 update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central 2020 Release Wave 1 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics 365 Business Central 2020 Release Wave 1.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.