web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Requisition Number sequence is changing randomly

(0) ShareShare
ReportReport
Posted on by 10

Hello,

A client of mine is having an issue where the Requisition Number sequence is randomly changing in the POP setup screen.  For example, they would force the number REQ000100 and it will correctly assign that number and the next one.  However, after some time, it just changes to an old number like REQ000080.  The client recently migrated data to a new company and only migrated open requisitions.  Still, it does not make sense to me for GP to randomly try to use an old number when there is a sequence established in the setup.

Client is on Dynamics GP 2016

Any help as to what might be causing this is greatly appreciated.

I have the same question (0)
  • Verified answer
    Lisa at AonC.com Profile Picture
    919 Super User 2025 Season 2 on at

    We too have seen this behavior.  I believe it is caused by the way that GP tries to backfill missing numbers in the sequences.  For PO and Receipts, there is a PSTL tool to set minimum numbers, but they haven't expanded the functionality to include Requisitions.   Our client saw it after deleting a Requisition.  

    I did create a feature request that you can review/vote for here:  Microsoft Idea  Â· PO Requisition Controls to prevent deleting Submitted/Rejected requisition (dynamics.com)

  • Verified answer
    Beat Bucher  GP Geek  GPUG All Star Profile Picture
    28,058 Moderator on at

    Hi Ricardo,

    I agree with Lisa.. that's an old bug (if it can be called a bug, Microsoft may say it's by design).. PSTL fixes the problem for POP, but not requisitions. I'd have to check if that was fixed in the latest 18.4 release from this fall.

  • Ricardo Carrillo Profile Picture
    10 on at

    Hi Lisa/Beat,

    Thank you very much for your insight. It seems that the only way to fix it is to fill the Requisition history table with thousands of old numbers so it doesn't continue changing the sequence. I have tried to replicate the behavior in a test environment and can't seem to do it though, which is very strange.

    Regardless, thank you for your help!

  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    14,093 Most Valuable Professional on at

    It would only go backwards if you delete an old requisition. That would restore its now unused number.

    When it gets new numbers it would then work its way forward skipping passed used numbers but filling gaps.

    A quick customisation with GP Power Tools could prevent the number from going backwards.

    Regards

    David

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 660 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 549 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 307 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans