Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / A unique document numb...
Microsoft Dynamics GP (Archived)

A unique document number could not be found

(0) ShareShare
ReportReport
Posted on by Chris Flood 655

One person receives this message when they try to print an edit list (of Manual Payments) in GP while 2 other users can print an edit list without any errors.

The fact that multiple users can print the edit list rules out possibilities such as:

  • The number of characters being too long
  • The document number being assigned to one or more transactions in the batch being deleted, and subsequently used by someone else - as this would produce this message for all users

One thought was security but this user has access to the Manual Payments Edit List (Manual Payments Posting Journal).

Do you have any ideas on what else could be the cause of this?

*This post is locked for comments

  • Verified answer
    Chris Flood Profile Picture
    Chris Flood 655 on at
    RE: A unique document number could not be found

    After testing this in more detail, the user was performing the function in a manner that caused the error.

    Once the corrective actions were performed, the user has been able to print the batch.

  • Suggested answer
    L Vail Profile Picture
    L Vail 65,271 on at
    RE: A unique document number could not be found

    Normally, what this means is that in the setup of Payables, the next document number has already been used. The Purchasing module had a habit of searching backward through the database to find a document number under certain instances. When it tried to generate the 'next document number' it found that that document number had already been used. Changing the next document number to a larger number normally solved the issue for a while, but not forever. GP included a tool in the PSTL module that prevents this from happening in POP at least. To engage it, you just check the box next to the item. Here's what it looks like:

    It may be a long shot, but it's an idea.

    Kind regards,

    Leslie

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,489 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,305 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans