Skip to main content

Microsoft Dynamics Business Central Cumulative Update Summary for May 2024.

 Hi Readers,

A New Month and a new set of cumulative updates.

Microsoft Have Released Cumulative Update for May 2024 for Business Central 23& 22.

Please find below the details of Cumulative Updates Released for Microsoft Business Central 23 & 22.

Below are the Links to Download the Latest Cumulative Update.

#msdyn365bc #cumulativeupdate

1. Title - Cumulative Update 23.7 for MSDYN365BC 2023 Wave 2 Update on-premises (BC23)

  Application Build No. - 23.7.18957

  Platform Build No.    -  23.0.18933

  Details of Update

  Download Link


2. Title - Cumulative Update 22.13 for MSDYN365BC 2023 Wave 1 Update on-premises (BC22)

  Application Build No. - 22.13.64344

  Platform Build No.    -  22.0.64336

  Details of Update

  Download Link


Application Hotfix in BC 23 - 

  • 499081 - The Error Call Stack field is empty when opening from the Error Messages Register page.
  • 522547 - Item Applications don't comply with Package Specific Tracking when Reservation exists.
  • 521675 - Unable to drill into the Cost Adjmt. Amount ($) value field within Statistics to view Value Entry Adjustments in the Posted Sales Invoice.
  • 522419 - When using the filtering function, bin contents move to another location without proper information if the connection to the item is lost.
  • 525535 - Item Security filter is not applied to the Item Availability by Event page.
  • 503053 - "Package No. must be equal to 'x' in item ledger entry: Entry No.=xxx. Current value is 'x'." error message when package tracking is enabled, and a job is used on a purchase order.
  • 507116 - Issue when printing bulk Transfer Orders.
  • 524078 - Posting Item Journal takes too long after environment update.
  • 498978 - "You have insufficient quantity of Item xxx on Inventory" error message when trying to post the consumption that is reserved to multiple Lot Tracked ILEs.
  • 503172 - Comments in the production bill of material (BOM) are not adopted correctly on the Production Order.
  • 504249 - The consumption journal does not take the Calculation Formula into account.
  • 488620 - When increasing the quantity of a released production order using the Pick + Forward flushing method, more components are picked than expected.
  • 504407 - "Warehouse handling is required for Entry Type = Output, OrderNo. = 101023, order Line No. = 10000." error message when trying to post a negative output from an output journal with a location, and the Enum "Prod. Output Whse. Handling" set as "No Warehouse Handling".
  • 490898 - "The record in table Warehouse Entry already exists. Identification fields and values: Entry No.='2'" error message when receiving a purchase order for subcontracting.
  • 522486 - Unable to add the Variant field by the personalization option in the Subcontracting Worksheet.
  • 523793 - After updating the Bal. Account No. field, the Bal. Non-Ded. VAT % field is not set, resulting in other related fields not being calculated.
  • 491022 - When adding comments to an opportunity, not all of the comments are displayed.
  • 522558 - The ApplicationArea Property for the Customer Statistics FactBox on the Sales Invoice page is set to Advanced instead of Basic, Suite.
  • 498734 - Orphaned surplus entry when creating the Service Credit Memo on a non-inventory item with a serial number.
  • 507359 - The warranty is incorrect when the Warranty Item with an assigned Service Item Group configured to create service items is used in a Sales Order to generate a service item.
  • 504518 - The Line Discount % field is deleted in the service line when changing the Fault Reason Code in a service order.
  • 504253 - "Warranty Date must have a value in Tracking Specification" error message when posting the Warehouse Shipment for an item with Serial Tracking and Warranty Date if the tracking is assigned by using the Serial Number field on the Warehouse Pick.
  • 506443 - The expiration date is not transferred to picklines when using item tracking in assembly orders.
  • 506467 - Meaningless placeholders exist in the copy document notification for the physical inventory orders.

Application Hotfix in BC 22 - 

  • 500943 - When using the filtering function, bin contents can move to another location without proper information if the connection to the item is lost.
  • 488261 - When increasing the quantity of a released production order using the Pick + Forward flushing method, more components are picked than expected.
  • 490332 - "The record in table Warehouse Entry already exists. Identification fields and values: Entry No.='2'" error message when receiving a purchase order for subcontracting.
  • 498010 - After updating the Bal. Account No. field, the Bal. Non-Ded. VAT % field is not set, resulting in other related fields not being calculated.

For information about the previous Cumulative update released for Business Central on Prem, Microsoft Dynamics NAV2018, BC14, BC20, BC21 & BC22 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.