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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

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

Re-use a previously deleted number sequence value

(1) ShareShare
ReportReport
Posted on by 8
Hello,
I have a scenario where I have added a custom field EDT XXXValue in the CustTransOpen table which is associated to a number sequence reference.
It should generate a new number sequence reference (e.g. 00001) whenever there are marked for transactions (i.e. records of SpecTrans).
However, if all marked records are unmarked (i.e. no spec trans association to the CustTransOpen) then the field value should be set to empty.
If the user wish to remark records, the value 00001 should be reused (if this value is not used in any CustTransOpen).
I have tried retrieving the value 00001 in the logic of spec trans delete and check if there are any CustTransOpen.XXXValue==00001.
If there are no existing records, then I am calling the logic NumberSeq::releaseNumber(numbersequenceID, 00001).
It is not working though.
Anyone knows how this could be done
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    303,354 Super User 2026 Season 1 on at
    HI Jason,
     
    Can you tell what exact business requirement you try to solve with the new field and the number sequence? What is the added value for the organization? 
     
    Anyway, did you setup the number sequence itself to have the field Continuous enabled? 
  • Verified answer
    Jason0810M Profile Picture
    8 on at
    Hello Andre,
    The business need is that a custom number sequence field needs to be added on CustTrans/VendTrans when doing settlement.
    All custTrans/vendtrans within same settlement logic needs to be filled with that number sequence (e.g. 0001).
    However, the field needs to be cleared if all the concerned settlements are cancelled.
    Therefore, the value 0001 is not being used anymore.
    If ever a new settlement is performed, the value 0001 should be available to be used again.
    I have managed to do it.
    I had set the numseq to Continuous and what was missing was setting the parameter _makeDecisionlater=true in the method NumberSeq::newGetNum when generating the number sequence.
    This fixed my issue.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

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

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 509 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 375

#3
Adis Profile Picture

Adis 268 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans