You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Batch requests bundle multiple operations into a single one and have the following advantages:
983
+
Batch Operations bundle multiple requests into a single one and have the following advantages:
980
984
981
985
* Reduces a number of requests sent to the Web API server. `Eachuserisallowedupto60,000APIrequests, perorganizationinstance, withinfiveminuteslidinginterval.` [More Info](https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/api-limits)
982
986
* Provides a way to run multiple operations in a single transaction. If any operation that changes data (within a single changeset) fails all completed ones will be rolled back.
983
987
* All operations within a batch request run consequently (FIFO).
984
988
985
-
DynamicsWebApi provides a straightforward way to execute Batch operations which may not always be simple to compose.
989
+
DynamicsWebApi provides a straightforward way to execute Batch Operations which may not always be simple to compose.
986
990
987
991
**Please Note!** By default, all operations that modify data, such as: CREATE, UPDATE, UPSERT, PUT and DELETE - are automatically made atomic (combined in Change Sets). You can change this behaviour by setting `inChangeSet` to `false`. [More Info](#controlling-change-sets)
The first two requests will be atomic (included in a Change Set) and the last one will be executed separately. So, if for some reason, there was an error during creation of an Email record, the whole operation won't be rolled back and the Contact and Order records will be created in the system.
1199
1203
1200
-
**Be extra careful** with an order of requests in a Batch Operation, especially if it has a combination of atomic and non-atomic operations in it. For example, if in an example above we move the creation of an Email record above Order it will create 2 separate change sets for the Contact and for the Order records.
1204
+
**Be extra careful** with an order of requests in a Batch Operation, especially if it has a combination of atomic and non-atomic operations in it. For example, if in an example above we move the creation of an Email record above Order - it will create 2 separate change sets for the Contact and for the Order records.
0 commit comments