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

Announcements

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

No series in Req Worksheet error "No. Series" does not update the "last used number."

(1) ShareShare
ReportReport
Posted on by 57
Hi Community,
 

I create a sales order and then go to the Requisition Worksheet to generate a purchase order based on this sales order. The first time this process is executed, it works correctly. However, when I attempt it a second time, it fails.The issue appears to be that the "No. Series" does not update the "last used number."

For example, if the last number is 7469 and I generate Purchase Order 7470 via the Requisition Worksheet, the system successfully creates the order. However, the "last used number" in the No. Series should update to 7470, but it remains at 7469. This causes a failure on the subsequent order.

 
Callstack:
Als u ondersteuning vraagt, geeft u de volgende details op om het probleem op te lossen:
Foutmelding: 
De record in tabel Inkoopkop bestaat al. Identificatievelden en waarden: Documenttype='Order',Nr.='01010'
Interne sessie-id: 
636f5de6-c91e-4496-8747-6dd02de8e186
Id van Application Insights-sessie: 
781d57fa-dbf9-4a30-bd7f-37c5d1db3697
Id van clientactiviteit: 
eb100238-93fe-405d-b555-2806c93b15f9
Tijdstempel van fout: 
2026-02-17T11:12:32.4701683Z
Telemetrie-id van de gebruiker: 
ac78a87a-bf09-4c06-a6fe-cd1f87896b99
AL-aanroepstack: 
"Sales Forecast Notifier"(CodeUnit 1854).PurchaseHeaderCommitted line 4 - Sales and Inventory Forecast by Microsoft version 27.4.45366.45675
"Sales Forecast Notifier"(CodeUnit 1854).CreateStockoutNotification line 4 - Sales and Inventory Forecast by Microsoft version 27.4.45366.45675
"Sales Forecast Notifier"(CodeUnit 1854).OnAfterTableInsert line 6 - Sales and Inventory Forecast by Microsoft version 27.4.45366.45675
"Req. Wksh.-Make Order"(CodeUnit 333).InsertHeader line 23 - Base Application by Microsoft version 27.4.45366.46024
"Req. Wksh.-Make Order"(CodeUnit 333).InsertPurchOrderLine line 19 - Base Application by Microsoft version 27.4.45366.46024
"Req. Wksh.-Make Order"(CodeUnit 333).CarryOutReqLineAction line 82 - Base Application by Microsoft version 27.4.45366.46024
"Req. Wksh.-Make Order"(CodeUnit 333).ProcessReqLineActions line 8 - Base Application by Microsoft version 27.4.45366.46024
"Req. Wksh.-Make Order"(CodeUnit 333).Code line 54 - Base Application by Microsoft version 27.4.45366.46024
"Req. Wksh.-Make Order"(CodeUnit 333).CarryOutBatchAction line 11 - Base Application by Microsoft version 27.4.45366.46024
"Carry Out Action Msg. - Req."(Report 493).UseOneJnl line 13 - Base Application by Microsoft version 27.4.45366.46024
"Carry Out Action Msg. - Req."(Report 493).OnPreReport(Trigger) line 4 - Base Application by Microsoft version 27.4.45366.46024
"Req. Worksheet"(Page 291).CarryOutActionMsg line 11 - Base Application by Microsoft version 27.4.45366.46024
"Req. Worksheet"(Page 291)."CarryOutActionMessage - OnAction"(Trigger) line 2 - Base Application by Microsoft version 27.4.45366.46024
 
 
 
Is this a known error and when will it get fixed? The New No. Series In Business Central - Business Central Geek 
 
Kind regards,
 
I have the same question (0)
  • Suggested answer
    Ben Baxter Profile Picture
    6,782 Super User 2026 Season 1 on at
    This is not a known error.  Can you check if you have any Customizations around the Purchase Order creation process?  If you have multiple extensions in the environment receiving the error, you can try removing them one at a time until you identify which one is causing the issue.
     
    Best Regards,
    Ben Baxter
    Accent Software Inc
  • Suggested answer
    Teagen Boll Profile Picture
    886 Super User 2026 Season 1 on at
    As another user mentioned its not a known error. I would double check your Purchase and Payable setup page. Make sure that the no. series for POs is entered correctly. Then check your no. series page and make sure you still have numbers available and that the options for POs are working correctly like this:
     
    If that doesnt work you could potentially try creating a new no. series for POs with a new numbering sequence (i.e. PO-00001 instead of 01010).
     
    If you still get the same error you may have an old PO record stuck in the PO table. You may need to get a developer to look or use a tool like the data editor (which you should use with extreme caution). You can download it here and I would look at the PO table with it to see if there are old PO records: Table Data Editor 2.0

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 > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,029 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,044 Super User 2026 Season 1

#3
Dhiren Nagar Profile Picture

Dhiren Nagar 1,026 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans