Skip to main content

#msdyn365bc 2023 Release Wave 1 - Avoid document number errors when you post item journals.

Hi Readers,

In this series we are discussing what's new in Business Central 2023 (Wave 1) a.k.a BC22.

This article we will discuss about - Avoid document number errors when you post item journals.

With this series we will understand what's new the product and learn it. 

Hope you like the series, please add comments to article.

#msdyn365bc #2023RW1

Business value:

  • To avoid or fix errors related to the order of document numbers when you post item journals, you can use the Renumber Document Numbers action before you post.

Feature details:

  • On the Item Journals page, the Document No. field is editable so that you can specify different document numbers for different journal lines, or the same document number for related journal lines.

  • If a number series is specified in the No. Series field on the item journal batch, document numbers for individual or grouped lines must be in sequential order when you post an item journal. If they aren't, you can't post the journal. 

  • To avoid problems with posting, you can use the Renumber Document Numbers action on the Item Journals page before you post the journal. 
  • If related journal lines were grouped by document number before you used the action, they'll stay grouped but might be assigned a different document number.
  • The Renumber Document Numbers action also works on filtered views.


  • Open Item Journal and Add Lines in the Item Journal.
  • Select Batch where No. Series is Defined.

  • Add Multiple Lines, you are either supposed to remember last no. used or you will key document No. randomly (as shown below). 

  • If you try to Post, System will warn about incorrect Document No.

  • For this Select Renumber Document Numbers as shown below.

  • This will update Document No. of all lines (If you apply filter, action will respect that filter).

For other articles related to What's New in Business Central 22, refer here.

Hope you learn and will be able to utilize this feature as Business Central 22 is available.  

Saurav Dhyani 


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.