Incoming Web Services and API Query : a lesson learned

Dynamics 365 ERP - Development

The API that copies data to Azure Data Lake failed after a Dynamics 365 upgrade to version 23, returning HTTP 408.
OData/API timeout in SaaS is set to 8 minutes and cannot be changed.
Telemetry revealed that the API was exceeding the timeout limit since the upgrade in December.
Analysis of Incoming Web Services calls showed a significant increase in processing time post-upgrade.
Comparison of queries from November to post-upgrade revealed minor differences that may have impacted performance.
FlowFields added to the API object were identified as potential causes of the increased processing time.
Removal of unused FlowFields resulted in a significant drop in execution time from 8 minutes to approximately 6 seconds.
Key takeaways include being cautious with adding fields to API queries, utilizing telemetry to identify regressions, and keeping data for longer periods when necessary.

Registered users can view the full text for FREE!