web
You’re offline. This is a read only version of the page.
close
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 / Finance | Project Operations, Human Resources, ... / Number sequence Preall...
Finance | Project Operations, Human Resources, ...
Answered

Number sequence Preallocation

(0) ShareShare
ReportReport
Posted on by YOG 414

HI All,

we have been having system performance issues (on Warehouse scanner and Sales order). Looking at environment activities on LCS, issue is caused by number sequence.

i have raised case with MSFT and they couldn't find perficular number sequence that is causing issue. They've recommended to use Preallocation feature to improve performance.

Current version

10.0.12 (10.0.507.20021) - Update 36 (7.0.5688.41472)

Business Issue

Users are frustrated due to slowness of system. System takes too much time releasing order to warehouse and much time picking/Packing order.

Questions

1. Do i have switch continuous sequences to non-continuous?

2. Do 'Quantity of numbers' 5 enough for all non continues number sequence (even for Lot id where multiple transactions are happing together?

I have the same question (0)
  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,160 Moderator on at

    1. What number sequences do you have set up for Continuous? You should only use Continuous for the nr seq where it's a legal requirement.

    2. I would try also with higher numbers than 5. Where did 5 come from?

  • YOG Profile Picture
    YOG 414 on at

    hi Nikolaos,

    1. That comes default out of box. nothing has been changed

    2. No. 5 is a minimum that system can accept

  • nmaenpaa Profile Picture
    nmaenpaa 101,160 Moderator on at

    1. I don't understand this statement. I asked "What number sequences do you have set up for Continuous? You should only use Continuous for the nr seq where it's a legal requirement.".

  • YOG Profile Picture
    YOG 414 on at

    hi Nikolaos,

    i have 319 sequences setup as Continuos. they are in different parts of system.

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,160 Moderator on at

    Ok, that's definetely a problem for performance. Please make all of them non-continuous, except the ones where you have a legal requirement to keep them continuous.

  • Verified answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 301,075 Super User 2025 Season 2 on at

    Hi YOG,

    Definitely, you have to use only continuous for number sequences related to voucher and invoice numbers. In some cases, there might be other number sequences required by accounting regulations which should be continuous.

    You mentioned that the numbers came out of the box. Probably you used the number sequence wizard to generate a quick setup. Unfortunately, this wizard also created continuous sequences which are not required and can cause slowness. This wizard is also creating defaults where you would get stuck as it will try to use duplicate voucher or invoice numbers. In my implementations, I always ignored the wizard and used my own experience to setup the number sequences manually.

  • YOG Profile Picture
    YOG 414 on at

    Thank you Andre/Nikolaos,

    I did change number sequences to Non-continuous and have been monitoring environment performance.  I have come across below query that is taking longer time continuously.  How can i get more details about this query?

    @P1 bigint,@P2 int)SELECT TOP 1 T1.NEXTREC,T1.NUMBERSEQUENCEID,T1.SESSIONID,T1.SESSIONLOGINDATETIME,T1.SESSIONLOGINDATETIMETZID,T1.STATUS,T1.TRANSID,T1.USERID,T1.MODIFIEDDATETIME,T1.MODIFIEDBY,T1.MODIFIEDTRANSACTIONID,T1.RECVERSION,T1.PARTITION,T1.RECID FROM NUMBERSEQUENCELIST T1 WHERE ((PARTITION=5637144576) AND ((NUMBERSEQUENCEID=@P1) AND (NEXTREC=@P2)))

  • Verified answer
    nmaenpaa Profile Picture
    nmaenpaa 101,160 Moderator on at

    Hi YOG,

    since the query is reading NumberSequenceList table, it's related to a continuous number sequence.

    With continuous number sequences, the system returns unused numbers to the NumberSequenceList table.

    The query could either be triggered by fetching next number for a continuous number sequence, or by the number sequence cleanup job.

    Most likely this query will not impact the performance of non-continuous number sequences at all.

  • YOG Profile Picture
    YOG 414 on at

    Thank you Andre/Nikolaos :)

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 551 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

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

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans