Microsoft Dynamics CRM (Archived)

ExecutMultipleRequest limitations

(0) Share

Report

Posted on by Community Member

What are the limitations with regards to the ExecutMultipleRequest?

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

Radu Chiribelea 6,667 on at

Like (1)

Report

Hi Miriam,

Please check following article: msdn.microsoft.com/.../jj863631.aspx

Run-time limitations

There are several constraints related to the use of the ExecuteMultipleRequest as described in the following list.

No recursion is allowed - ExecuteMultipleRequest cannot invoke ExecuteMultipleRequest. An ExecuteMultipleRequest found in the request collection will generate a fault for that request item.

Maximum batch size – there is a limit to how many requests can be added to a request collection. If that limit is exceeded, a fault is thrown before the first request is ever executed. A limit of 1000 requests is typical though this maximum amount can be set for the Microsoft Dynamics 365 deployment. The deployment setting for this limit is BatchSize.

Throttling of concurrent calls – for Microsoft Dynamics 365 (online) there is a limit of 2 concurrent ExecuteMultipleRequest executions per organization. If that limit is exceeded, a “Server Busy” fault is thrown before the first request is ever executed. For an on-premises deployment, throttling is not enabled by default. The deployment setting for this limit is ExecuteAsyncPerOrgMaxConnectionsPerServer.

Was this reply helpful? Yes No
Suggested answer

Michel van den Brink 4,697 on at

Like (0)

Report
Hello Miriam,

Please take a look at this article about how ExecuteMultiple works and what its limitations are
https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/org-service/use-executemultiple-improve-performance-bulk-data-load

A quick overview of the limitations:

No recursion is allowed

ExecuteMultipleRequest cannot invoke ExecuteMultipleRequest. An ExecuteMultipleRequest found in the request collection will generate a fault for that request item.

Maximum batch size is typically 1000

there is a limit to how many requests can be added to a request collection. If that limit is exceeded, a fault is thrown before the first request is ever executed. A limit of 1000 requests is typical though this maximum amount can be set for the Dynamics 365 deployment. The deployment setting for this limit is BatchSize.

Maximum 2 concurrent executions per organization

If that limit is exceeded, a “Server Busy” fault is thrown before the first request is ever executed. For an on-premises deployment, throttling is not enabled by default. The deployment setting for this limit is ExecuteAsyncPerOrgMaxConnectionsPerServer.

Hope this helps you!

If you found my answer helpful, please help the community by marking it as verified :-)

Was this reply helpful? Yes No
Suggested answer

gdas 50,091 Moderator on at

Like (0)

Report

H Miriam,

Radu is correct ,please go through the details in msdn reference shared by Radu.

Was this reply helpful? Yes No