This article applies to Microsoft Dynamics 365 Business Central 2019 Release Wave 2 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 2019 Release Wave 2. Updates are intended for new and existing customers who are running Microsoft Dynamics Released Updates for Microsoft Dynamics 365 Business Central 2019 Release Wave 2.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:
Platform hotfixes
|
ID |
Title |
|
363728 |
Bookmarks that are defined in profile configurations cannot be customized from user personalization if the Application and Base Application are installed with specific versions. |
|
365426 |
Column headers are not aligned correctly when you enable personalization and hide columns in the Web client in a browser that is not maximized. |
|
363773 |
The symbol file of an application to be published has been switched to be generated on the server for both Rapid Application Development (RAD) and normal server publishing. |
Application hotfixes
|
ID |
Title |
Functional Area |
|
36137+A8:C249 |
"You do not have the following permissions on table Posted Whse. Receipt Line: Execute" error message displays when undo receipts and have the Starter Pack license. |
Administration |
|
362583 |
Error message displays in the security filter when you post purchase receipts. |
Administration |
|
362980 |
Update the text for the Log Web Request option in Currency Exchange Rate services. |
Administration |
|
360282 |
"The Currency already exists" error message displays when you un-apply the payment with the foreign currency. |
Finance |
|
362936 |
You must have Direct Modify permissions on purchase orders to be able to approve workflow. |
Finance |
|
363837 |
An overflow error message displays when you try to post a purchase intercompany invoice with Your Reference setup. |
Finance |
|
352423 |
The Edit function in Excel assigns an incorrect journal template when you publish batches. |
Finance |
|
365277 |
The Notify Sender option in workflows does not send a notification to the requestor. |
Finance |
|
363397 |
The MessageLine Text parameter of the ShowError function in codeunit is too short. |
Fixed Assets |
|
361456 |
It is impossible to set the Due Date field on the purchase invoice via API call. |
Integration |
|
361105 |
The Warehouse Document-Print codeunit uses the HideDialog parameter in PrintInvtPutAwayHeader, PrintInvtMovementHeader, PrintInvtPickHeader functions as a ShowDialog parameter. |
Inventory |
|
363808 |
"The length of the string is XXX, but it must be less than or equal to 250 characters." error message displays if you try to open the Bin Contents page and you have a warehouse employee with many locations set up as Bin Mandatory. |
Inventory |
|
363826 |
The job status is set to planning after you copy a job from another one. |
Jobs |
|
360378 |
Double output quantity is recorded when you finish a production order that has a work center with backward flushing and the output has been recorded in an output journal. |
Manufacturing |
|
361101 |
"Error when calculating forward. Calendar is not available after DD/MM/YY for Work Center X" error message displays when you refresh a production order where the routing contains a send-ahead quantity with a wait time. |
Manufacturing |
|
361840 |
You can certify routings for deleted work centers. |
Manufacturing |
|
364325 |
When you open the Routing page, the Prod. Order Line Bin Code field is updated with bin code from Work center instead of maintaining the bin code from the header. |
Manufacturing |
|
364799 |
An overflow error message displays when you enter a value in the Order No. field on a consumption journal if the production order has a description of more than 50 characters. |
Manufacturing |
|
365173 |
"Error when calculating forward. Calendar is not available after 30.12.22 for Machine Center XXX." error message displays when you enter a routing ending date or time or the Schedule Manually field is chosen. |
Manufacturing |
|
365634 |
The Segment Description field is not populated in the Opportunity card. |
Marketing |
|
359371 |
The VAT clause is not validated when you run the Get Posted Document Lines to Reverse function and select the posted shipment. |
Sales |
|
362734 |
When you run an available to promise (ATP) calculation a second time for a sales order without any changes on the supply side, The Earliest Shipment Date and Planned Delivery Date fields are incorrect. |
Sales |
|
361947 |
The Line Amount Excluding VAT mismatches in the posted sales invoice and general ledger entry for partial invoices. |
Sales |
|
363218 |
"The target email address has not been specified" error message displays in the update of Customer Statements report. |
Sales |
|
364367 |
You can post the sales order without Unit of Measure (UoM). |
Sales |
|
365627 |
Too many modifications of Requisition Lines. |
Sales |
|
362767 |
The recurring sales line is displayed on sales quotes although no customer is added. |
Sales |
|
362311 |
The purchase order with the Qty. to Receive field is not converted by the VAT Rate Change tool when the Default Quantity to Receive field is set to Blank. |
VAT/Sales Tax/Intrastat |
|
362220 |
The Pick Worksheet function does not create a pick for all assembly component lines when one component has the lot tracking. |
Warehouse |
Local application hotfixes
AT - Austria
|
ID |
Title |
Functional Area |
|
366249 |
New changes are in the VAT Statement on July 1st, 2020 in the Austrian version. |
Finance |
AU - Australia
|
ID |
Title |
Functional Area |
|
360909 |
The Home Page and Email ID fields contain incorrect values in the printed posted purchase receipt in the Australian version. |
Purchase |
BE - Belgium
|
ID |
Title |
Functional Area |
|
362832 |
A request to backport events in the Belgian version. |
Administration |
|
363738 |
The Sales-Document Test report checks on an incorrect variable for the VAT Registration No. and Enterprise No. fields in the Belgian version. |
Finance |
|
363393 |
The status of the lines and the amounts is not correctly updated if you manually apply or un-apply a line in the CODA process in the Belgian version. |
Finance |
|
362885 |
The SEPA Direct Debit - SWIFT code in the Domiciliation Journal is not needed in the Belgian version. |
Finance |
CZ - Czech
|
ID |
Title |
Functional Area |
|
360494 |
The Cash Payment Limit field does not work in the Czech version. |
Cash Management |
|
361580 |
VAT entries are incorrect when you use the Post Advance VAT Option that is set to Never in a Sales Advance Letter in the Czech version. |
Finance |
DACH
|
ID |
Title |
Functional Area |
|
363815 |
The index.xml file that is created from the Business Data Export action cannot be validated if German special characters are included in Export Table Name, Export File Name, and Export Field Name in the DACH version. |
Finance |
|
357979 |
The Batch Post Sales Orders report (Web client) with the Print option is incorrect in the DACH version. |
Sales |
DE - Germany
|
ID |
Title |
Functional Area |
|
357979 |
The Batch Post Sales Orders report (Web client) with the Print option is incorrect in the German version. |
Sales |
ES - Spain
|
ID |
Title |
Functional Area |
|
363339 |
"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 |
|
363463 |
The <PrestacionServicios> node is not exported in the Sales Credit Memos by using EU Service for the SII module in the Spanish version. |
Finance |
IT - Italy
|
ID |
Title |
Functional Area |
|
361961 |
If you apply a Withholding Tax - Soc. Security purchase invoice to the related payment, the external document number on the invoice is not reported as the withholding social security information in the Italian version. |
Finance |
NA - North America
|
ID |
Title |
Functional Area |
|
362894 |
When you use the Canadian EFT, there is no option for Settlement Date in the File Header in the North American version. |
Cash Management |
|
352093 |
If a default dimension value is not specified prior to generating an EFT file, the payment journal cannot be posted in the North American version. |
Cash Management |
|
362994 |
The sales tax calculation is incorrectly displayed on the Purchase Invoice Line subpage when the Expense/Capitalize option is enabled in the North American version. |
Purchase |
NL - Netherlands
|
ID |
Title |
Functional Area |
|
363006 |
The generic payment file exports non-EUR transactions in the Dutch version. |
Cash Management |
|
364804 |
Bank/Giro journals only allow entries in LCY that will affect vendor ledger entries in the Dutch version. |
Cash Management |
|
363802 |
The first time you enter lines in the Bank/Giro Journal, the Date field on the lines is overwritten by the Date field in the header in the Dutch version. |
Finance |
NO - Norway
|
ID |
Title |
Functional Area |
|
363667 |
SAF-T files include the Company Information, VAT Registration No., and Registration No. fields in the Norwegian version. |
Finance |
|
363672 |
The XML file for transactions is missing information in SAF-T Export Line for the Transaction Type property and Batch ID field in the Norwegian version. |
Finance |
|
362279 |
An electronic invoice in EHF 3.0 format cannot be validated when the ISO code is blank in the Country Code field in the Norwegian version. |
Finance |
|
362898 |
The KID No. field is incorrect in the (electronic) reminder in the Norwegian version. |
Finance |
|
361934 |
An electronic reminder in EHF 3.0 format cannot be validated when the Your Reference field has not been set on the reminder in the Norwegian version. |
Finance |
RU - Russia
|
ID |
Title |
Functional Area |
|
359828 |
"The length of the string is 20, but it must be less than or equal to 10 characters" error message displays when you run Item Write-off act TORG-16 in the Russian version. |
Inventory |
|
360299 |
The M-4 reports lost a line in a print form in the Russian version. |
Inventory |
Resolution
How to obtain the Microsoft Dynamics 365 Business Central 2019 Release Wave 2 files
This update is available for manual download and installation from the Microsoft Download Center.
Update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2
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 2019 database:
|
Country |
Hotfix package |
|
AT - Austria |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 AT package |
|
AU - Australia |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 AU package |
|
BE - Belgium |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 BE package |
|
CH - Switzerland |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 CH package |
|
CZ- Czech |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 CZ package |
|
DE - Germany |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 DE package |
|
DK - Denmark |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 DK package |
|
ES - Spain |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 ES package |
|
FI - Finland |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 FI package |
|
FR - France |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 FR package |
|
IS - Iceland |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 IS package |
|
IT - Italy |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 IT package |
|
NA - North America |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NA package |
|
NL - Netherlands |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NL package |
|
NO - Norway |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NO package |
|
NZ - New Zealand |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 NZ package |
|
RU - Russia |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 RU package |
|
SE - Sweden |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 SE package |
|
UK - United Kingdom |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 UK package |
|
All other countries |
Download update 15.9 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 W1 package |
How to install a Microsoft Dynamics 365 Business Central 2019 Release Wave 2 update
See How to install a Microsoft Dynamics 365 Business Central 2019 Release Wave 2 update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central 2019 Release Wave 2 installed to apply this hotfix.
More Information
See more information about software update terminology and Microsoft Dynamics 365 Business Central 2019 Release Wave 2.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
