Skip to main content

Microsoft Dynamics Business Central Cumulative Update Summary For February 2021.

Hi Readers,

Microsoft Have Released Cumulative Update for February 2021 for Business central 14, 15, 16 & 17.

Please find below the details of Cumulative Updates Released for Microsoft Business Central 14, 15, 16 and 17.

Below are the Links to Download the Latest Cumulative Update.

#msdyn365bc14 #msdyn365bc15 #msdyn365bc16 #msdyn365bc17

1. Title - Cumulative Update 17.4 for MSDYN365BC 2020 Wave2 Update on-premises (BC17)

  Application Build No. - 17.4.21531

  Platform Build No. - 17.0.21516

  Local versions included - AT,AU,BE,CH,CZ,DE,DK,ES,FI,FR,IS,IT,NA,NL,NO,NZ,RU,SE,UK

  Details of Update

  Download Link

  Docker Pull Request - Get-BCArtifactUrl -type OnPrem -version 17.4 -country w1

  ** Replace w1 with local version that you need.

2. Title - Update 16.10 for Microsoft Dynamics 365 Business Central 2020 Release Wave 1 (BC16)

  Application Build No. - 16.10.21502

  Platform Build No. - 16.0.21469

  Local versions included - AT,AU,BE,CH,CZ,DE,DK,ES,FI,FR,IS,IT,NA,NL,NO,NZ,RU,SE,UK

  Details of Update

  Download Link

  Docker Pull Request - Get-BCArtifactUrl -type OnPrem -version 16.10 -country w1

  ** Replace w1 with local version that you need.

3. Title - Update 15.15 for Microsoft Dynamics 365 Business Central 2019 Release Wave 2 (BC15)

  Application Build No. - 15.15.46359

  Platform Build No. - 15.0.46345

  Local versions included - AT,AU,BE,CH,CZ,DE,DK,ES,FI,FR,IS,IT,NA,NL,NO,NZ,RU,SE,UK

  Details of Update

  Download Link

  Docker Pull Request - Get-BCArtifactUrl -type OnPrem -version 15.15 -country w1

  ** Replace w1 with local version that you need.

4. Title - Cumulative Update 21 for Microsoft Dynamics 365 Business Central April'19 on-premises (BC14)

  Application Build No. - 14.22.46358

  Platform Build No. - 14.0.46351

  Local versions included - AT,AU,BE,CH,CZ,DE,DK,ES,FI,FR,IS,IT,NA,NL,NO,NZ,RU,SE,UK

  Details of Update

  Download Link

  Docker Pull Request - Get-BCArtifactUrl -type OnPrem -version 14.22 -country w1

  ** Replace w1 with local version that you need.


Platform Hotfix in Business Central 17 -

  • 386594 - The Removed system filter is re-added if another filter with option values is added.
  • 384627 - Selecting Run and Start Debugging in Visual Studio Code does not deploy any extension and start debug.
  • 387801 - The Lookup, AssistEdit, and DrillDown actions are not working with the NavigatePage (wizard) page types if the visibility is triggered dynamically.
  • 379275 - Some custom pages might become non-editable when migrated to version 17.x for Microsoft Dynamics 365 Business Central 2020 Release Wave 2 from 15.x.
  • 386536 - Sometimes the OData batch request returns 500 InternalServerError while another response was expected.
  • 385830 - The Bookmarked Page Search option of Business Central Version 17.1 Role Center is not working in both online and on-premises.
  • 384330 - Microsoft Dynamics Business Central behind a reverse proxy requires X-Forwarded-Proto headers.
  • 385833 - A telemetry improvement to speed up investigation of login issues.
  • 386252 - The default SQL Server Database Compatibility Level for the Business Central database is set to SQL Server 2014 even though the earlier version of SQL supported is SQL Server 2016.
  • 385815 - Added a telemetry for API endpoint authorization scheme.
  • 385199 - Microsoft Dynamics Business Central behind a reverse proxy requires X-Proto headers.
  • 384699 - Fixes the SSL certificate subject validation for Delta Service.
  • 383035 - The NavDrilldownAction method is not supported.
  • 378881 - Date formats that are printed in an invoice are not following ISO date formats in several locales.

Platform Hotfix in Business Central 16 -

  • 385198 - Microsoft Dynamics Business Central behind a reverse proxy requires X-Proto headers.
  • 386569 - When using Subpages or FactBoxes, the indirect permissions and direct permissions for the pages do not work.

Platform Hotfix in Business Central 15 -

  • 385197 - Microsoft Dynamics Business Central behind a reverse proxy requires X-Proto headers.
  • 386568 - When using Subpages or FactBoxes, the indirect permissions and direct permissions for the pages do not work.

Platform Hotfix in Business Central 14 -

  • 380500 - Microsoft Dynamics Business Central behind a reverse proxy requires X-Proto headers.
  • 386202 - When using Subpages or FactBoxes, the indirect permissions and direct permissions for the pages do not work.

For information about the previous Cumulative update released for Business Central on Prem, Microsoft Dynamics NAV 2015, NAV 2016, NAV 2017 & NAV 2018 please Navigate to Hotfix Label or follow the Link.


Regards,
Saurav Dhyani

www.sauravdhyani.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.