Avoid document number errors when you post project journals
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | - | Apr 2025 |
Business value
Business Central helps reduce or eliminate friction when you work with documents and journals. If you use a number series for project journal batches, you won't be able to post the journal if the document numbers aren't in consecutive order. To avoid getting stuck, you can fix errors related to the order of document numbers when you post project journals.
Feature details
On the Project 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 project journal batch, document numbers for individual or grouped lines must be in sequential order when you post a project journal. If they aren't, you can't post the journal. To avoid getting stuck, you can use the Renumber Document Numbers action on the Project 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.
We'd like to thank our community for your valuable contributions to Microsoft’s open source BusinessCentralApps repo on GitHub.
Tell us what you think
Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.