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

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.