Small and medium business | Business Central, N...

Insert Sales Record with API

(1) Share

Report

Posted on by HeinKruger

Hi,
We got a question from a SAAS client about the limitations of inserts of Sales Documents through various API's. Their concern is that deadlocks will occur.

Question:
What is that maximum amount of inserts that BC can handle on one record before a deadlock will occur?
If we have Three API's that will insert randomly at anytime into Sales Header & Sales Lines with approximatly 3000 records each per day will this cause deadlocks?

The proposed solution is to give the API that will have the most inserts its own buffer tables (an exact replica of the Sales Header and Lines) and then use a job queue to systematically import the data, but I'm not convinced that it is necesarry.

Thanks

Categories:

Dynamics 365 Business Central

All responses (2)

Answers (0)

Suggested answer

Kamal Khakhkhar 443 on at

Like (0)

Report

Insert Sales Record with API

Hii There,

As per your requirement you can try this like below mentioned. Thank you, Yun Zhu.

https:/yzhums.com/6117/

Thank You.

Kamal Khakhkhar
Suggested answer

Tech-Lucky 1,026 on at

Like (0)

Report

Insert Sales Record with API

check this out might be usefull for you

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/performance/performance-developer#database-locking-caused-by-web-service-calls

Database locking caused by web service calls

Don't insert child records belonging to the same parent record in parallel. This condition causes locks on both the parent table and the integration record table because parallel calls try to update the same parent record. The solution is to wait for the first call to finish or use OData $batch, which will make sure calls get run one after another.