Overview
This update replaces previously released updates. You should always install the latest update.
After you install this hotfix, you might have to update your license to gain access to new objects that are included in this or a previous update. (This applies only to customer licenses.)
For a list of updates that were released for Microsoft Dynamics 365 Business Central 2022 Release Wave 2, see released updates for Microsoft Dynamics 365 Business Central 2022 Release Wave 2. Updates are intended for new and existing customers who are running Microsoft Dynamics Released Updates for Microsoft Dynamics 365 Business Central 2022 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.
Application hotfixes
|
ID |
Title |
Functional Area |
|
479613 |
The filter doesn't work on the date field of the Bank Account Ledger Entries on the Bank Account Reconciliation page. |
Cash Management |
|
474935 |
The Dampener Quantity value is not used when dealing with SKU. |
Inventory |
|
479839 |
The Inventory Valuation - Cost Specification report and the Inventory Valuation report are different. |
Inventory |
|
480341 |
The Unit Price in the lines does not update unless the Quantity field is changed when changing the Campaign No. in the header of a purchase order. |
Purchase |
|
468428 |
The dialog message is vague and misleading when changing a dimension code on a Sales Order Header. |
Sales |
|
480317 |
Unable to post a Sales Prepayment Invoice without defining the Invoice Rounding Account to the Customer Posting Group. |
Sales |
Local application hotfixes
CZ- Czech
|
ID |
Title |
Functional Area |
|
479836 |
The compensation posting does not transfer the variable symbol to the new customer leger entries or vendor leger entries in the Czech version. |
Finance |
|
478404 |
Issue with the cash flow and advance letter in the Czech version. |
Finance |
|
479752 |
Issue when posting a receipt of a purchase order with bond to the Cash Desk in the Czech version. |
Purchase |
|
479106 |
Error when there's a Reverse Charge in the Suggest VAT Control Report in the Czech version. |
VAT/Sales Tax/Intrastat |
DE - Germany
|
ID |
Title |
Functional Area |
|
480074 |
ELSTER rejects the VAT file created from the Business Central in the German version. |
VAT/Sales Tax/Intrastat |
Regulatory features
|
ID |
Title |
Functional Area |
Changed Objects |
|
475854 |
Issue with the new G/L Register for each invoice in the General Journal. |
Financial Management |
ExportGLEntriesTaxAudit.Report Extensions: FECAuditFile |
|
459981 |
Issue with Audit Files Export. |
Financial Management |
XMLDOMManagement.Codeunit Extensions: SAFTModificationDK AuditFileExport SAF-T |
Local regulatory features
AT - Austria
|
ID |
Title |
Functional Area |
Changed Objects |
|
459981 |
Issue with Audit Files Export in the Austrian version. |
Financial Management |
XMLDOMManagement.Codeunit Extensions: SAFTModificationDK AuditFileExport SAF-T |
AU - Australia
|
ID |
Title |
Functional Area |
Changed Objects |
|
478613 |
Issue with the Payment Times report in the Australian version. |
Financial Management |
CompanySize.Table CompanySizes.Page Customer.Table CustomerCard.Page DataClassificationEvalData.Codeunit GenJournalLine.Table PaymentJournal.Page d365automation.permissionset d365basic.permissionset d365basicisv.permissionset d365busfullaccess.permissionset d365read.permissionset d365teammember.permissionset d365vendoredit.permissionset intelligentcloud.permissionset PostedGenJournalLine.Table PurchaseHeader.Table PurchaseInvoice.Page PurchaseJournal.Page PurchaseOrder.Page Vendor.Table VendorCard.Page VendorLedgerEntries.Page VendorLedgerEntry.Table DataClassEvalDataCountry.Codeunit FinanceManagerRC.Page PaymentApplicationBuffer.Table PaymentPeriodSetup.Page PaymentPeriodSetup.Table PaymentPracticesReporting.Report PaymentReportingMgt.Codeunit UpdateDtldCVLedgerEntries.Codeunit syncdepfldpaymentpractices.codeunit local.permissionset localread.permissionset UPGFR.Codeunit UpgradeTagDefCountry.Codeunit PaymentPractices.Report PaymentPracticesMgt.Codeunit UPGGB.Codeunit companysizes.page Extensions: APIV1 APIV2 PaymentPractices |
DK - Denmark
|
ID |
Title |
Functional Area |
Changed Objects |
|
471285 |
Issue when uploading a .csv file with accounting data to Regnskab Basis in the Danish version. |
Financial Management |
XMLDOMManagement.Codeunit Extensions: SAFTModificationDK AuditFileExport SAF-T |
|
459981 |
Issue with Audit Files Export in the Danish version. |
Financial Management |
XMLDOMManagement.Codeunit Extensions: SAFTModificationDK AuditFileExport SAF-T |
FR - France
|
ID |
Title |
Functional Area |
Changed Objects |
|
475854 |
Issue with the new G/L Register for each invoice in the General Journal. |
Financial Management |
ExportGLEntriesTaxAudit.Report Extensions: FECAuditFile |
MX - Mexico
|
ID |
Title |
Functional Area |
Changed Objects |
|
477878 |
Update the receiver information in CFDI invoices and the CartaPorte complement in the Mexican version. |
Financial Management |
DataClassEvalDataCountry.Codeunit DocumentHeader.Table EInvoiceMgt.Codeunit SATAddress.Table SATAddresses.Page Location.Table LocationCard.Page local.permissionset PostedSalesCreditMemo.Page PostedSalesInvoice.Page PostedSalesShipment.Page SalesCrMemoHeader.Table SalesCreditMemo.Page SalesHeader.Table SalesInvoice.Page SalesInvoiceHeader.Table SalesOrder.Page SalesShipmentHeader.Table ShiptoAddress.Page ShiptoAddress.Table UPGMXCFDI.Codeunit UpgradeTagDefCountry.Codeunit |
NO - Norway
|
ID |
Title |
Functional Area |
Changed Objects |
|
459981 |
Issue with Audit Files Export in the Norwegian version. |
Financial Management |
XMLDOMManagement.Codeunit Extensions: SAFTModificationDK AuditFileExport SAF-T |
NZ - New Zealand
|
ID |
Title |
Functional Area |
Changed Objects |
|
478613 |
Issue with the Payment Times report in the New Zealand version. |
Financial Management |
CompanySize.Table CompanySizes.Page Customer.Table CustomerCard.Page DataClassificationEvalData.Codeunit GenJournalLine.Table PaymentJournal.Page d365automation.permissionset d365basic.permissionset d365basicisv.permissionset d365busfullaccess.permissionset d365read.permissionset d365teammember.permissionset d365vendoredit.permissionset intelligentcloud.permissionset PostedGenJournalLine.Table PurchaseHeader.Table PurchaseInvoice.Page PurchaseJournal.Page PurchaseOrder.Page Vendor.Table VendorCard.Page VendorLedgerEntries.Page VendorLedgerEntry.Table DataClassEvalDataCountry.Codeunit FinanceManagerRC.Page PaymentApplicationBuffer.Table PaymentPeriodSetup.Page PaymentPeriodSetup.Table PaymentPracticesReporting.Report PaymentReportingMgt.Codeunit UpdateDtldCVLedgerEntries.Codeunit syncdepfldpaymentpractices.codeunit local.permissionset localread.permissionset UPGFR.Codeunit UpgradeTagDefCountry.Codeunit PaymentPractices.Report PaymentPracticesMgt.Codeunit UPGGB.Codeunit companysizes.page Extensions: APIV1 APIV2 PaymentPractices |
SE - Sweden
|
ID |
Title |
Functional Area |
Changed Objects |
|
473092 |
Issue with the Payment Times report for large companies in the Swedish version. |
Financial Management |
CompanySize.Table CompanySizes.Page Customer.Table CustomerCard.Page DataClassificationEvalData.Codeunit GenJournalLine.Table PaymentJournal.Page d365automation.permissionset d365basic.permissionset d365basicisv.permissionset d365busfullaccess.permissionset d365read.permissionset d365teammember.permissionset d365vendoredit.permissionset intelligentcloud.permissionset PostedGenJournalLine.Table PurchaseHeader.Table PurchaseInvoice.Page PurchaseJournal.Page PurchaseOrder.Page Vendor.Table VendorCard.Page VendorLedgerEntries.Page VendorLedgerEntry.Table DataClassEvalDataCountry.Codeunit FinanceManagerRC.Page PaymentApplicationBuffer.Table PaymentPeriodSetup.Page PaymentPeriodSetup.Table PaymentPracticesReporting.Report PaymentReportingMgt.Codeunit UpdateDtldCVLedgerEntries.Codeunit syncdepfldpaymentpractices.codeunit local.permissionset localread.permissionset UPGFR.Codeunit UpgradeTagDefCountry.Codeunit PaymentPractices.Report PaymentPracticesMgt.Codeunit UPGGB.Codeunit companysizes.page Extensions: APIV1 APIV2 PaymentPractices |
Resolution
How to obtain the Microsoft Dynamics 365 Business Central 2022 Release Wave 2 files
This update is available for manual download and installation from the Microsoft Download Center.
Update 21.11 for Microsoft Dynamics 365 Business Central 2022 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 2022 database.
|
Country |
Hotfix package |
|
AT - Austria |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 AT package |
|
AU - Australia |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 AU package |
|
BE - Belgium |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 BE package |
|
CA - Canada |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 CA package |
|
CH - Switzerland |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 CH package |
|
CZ- Czechia |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 CZ package |
|
DE - Germany |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 DE package |
|
DK - Denmark |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 DK package |
|
ES - Spain |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 ES package |
|
FI - Finland |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 FI package |
|
FR - France |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 FR package |
|
GB - United Kingdom |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 UK package |
|
IN - India |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 IN package |
|
IS - Iceland |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 IS package |
|
IT - Italy |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 IT package |
|
MX - Mexico |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 MX package |
|
NL - Netherlands |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 NL package |
|
NO - Norway |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 NO package |
|
NZ - New Zealand |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 NZ package |
|
RU - Russia |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 RU package |
|
SE - Sweden |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 SE package |
|
US - United States |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 US package |
|
All other countries |
Download update 21.11 for Microsoft Dynamics 365 Business Central 2022 Release Wave 2 W1 package |
How to install a Microsoft Dynamics 365 Business Central on-premises 2022 Release Wave 2 update
See How to install a Microsoft Dynamics 365 Business Central 2022 Release Wave 2 update.
Prerequisites
You must have Microsoft Dynamics 365 Business Central 2022 Release Wave 2 installed to apply this hotfix.
More information
See more information about software update terminology and Microsoft Dynamics 365 Business Central 2022 Release Wave 2.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
