...
Based on your environment configurations, when the Batch size increases, the Snap might fail because of an API limitation and displays the following error message:
Number of requests exceeded the limit of 6000 over the time window of 300 secondsRefer to Service protection API limits - Finance & Operations for more information.
Workaround: You must decrease the batch size and retry.The Snap fails and updates the error view with the error message from API when you pass invalid values for a mandatory field.
Known Issues
NoneThe Microsoft Dynamics 365 Finance and SCM Update Snap displays the following errors when we run the batch process with the error view enabled.
500 ( Internal Server Error)
Socket timeout error
Read timed out error
Workaround: Increase the Timeout value to 500 or more and also decrease the batch size, along with the default retry properties.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document
|
|
| Requires the data that you need to update. |
Output | Document
|
|
| The data is written to the endpoint. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. | |||
...