Microsoft D365 CRM/CE request limits/allocations and API Limits
Article ID: KB0074714
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud Integration - Connect ( Scribe ) | - |
Description
Summary
In 2019 Microsoft introduced service protection API limits to the Common Data Service on its Power Platform. Customers using TIBCO Cloud™ Integration - Connect, TIBCO Scribe® Online, and TIBCO Scribe® Insight to connect with Dynamics 365 CE/CRM cloud applications or the Common Data Service might encounter these API limits.
The total number of API requests is limited by each user, per organization instance, within a five-minute sliding window. The number of concurrent requests is also limited. API calls made from plug-in code does not count against this external API request limit. See this article from Microsoft for more information about the nature of the API limits: (https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/api-limits).
It is recommended to read this post to become familiar with how the limits work and with the associated error messages. (https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations#microsoft-power-platform-requests-allocations-based-on-licenses).
These licensing changes are scheduled to be enforced/metered after a transition period on October 1, 2020, or the expiration of your current Office 365 subscription term, whichever is longer: (https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#how-does-the-change-to-powerapps-and-microsoft-flow-use-rights-for-office-365-applications-affect-me-will-my-existing-powerapps-applications-and-microsoft-flow-workflows-continue-to-work).
When one of these limits is exceeded, an exception will be thrown by Dynamics 365 CE/CRM.
If you have any questions regarding your user or tenant API request limits/allocations within D365 CE/CRM, please open a ticket with Microsoft Support.
Affected Users
TIBCO Cloud™ Integration, TIBCO Scribe® Online, and TIBCO Scribe® Insight users may see error messages generated from the existing API limits/allocations: (https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/api-limits#what-happens-when-the-limit-is-exceeded).
Many other connectors work with APIs that enforce API rate limits. These errors are generally shown as row errors or fatal errors in your Execution History and Agent logs.
To reduce the number of transient errors that could interrupt data processing, TIBCO has upgraded its TIBCO Scribe® Online connectors for Microsoft D365 CRM/CE and Microsoft Common Data Service and the corresponding TIBCO Scribe® Insight adapter to perform retry logic when the error response from the service specifies the amount of time to wait before sending more requests. The initial instances of these errors will not be reported by the connectors or adapter, but instead will be handled automatically. For TIBCO Cloud™ Integration and TIBCO Scribe® Online, the retries will be recorded in agent logs. After 3 retries, the connectors will stop retrying and the error from Microsoft will be passed through and will be visible in Execution History. For TIBCO Scribe® Insight users, the adapter follows the same retry logic and after 3 retries the error will be visible in the Execution Log.
The update for TIBCO Scribe® Insight is available as TIBCO Scribe® Insight Adapter for Microsoft Dynamics 365 And CRM 5.6.2 hotfix 5. See this article for information about the hotfix.
https://support.tibco.com/s/article/TIBCO-Scribe-Insight-Adapter-for-Microsoft-Dynamics-365-And-CRM-5-6-2-hotfix-5-is-now-available
Some users may still encounter limits or allocations based on integration design. There are configuration settings in TIBCO Scribe® Connectors/Adapters to help reduce the number of API hits, such as the Maximum Batch Size and Maximum Batch Threads settings on your connection configuration.
Best Practices
Many users can resolve limit/allocation errors and/or prepare for rate limit licensing enforcement by using existing connector features to help mitigate excessive API usage. Review the following TIBCO Scribe® features as you (re)design integrations with D365 CE/CRM:
Timeline
In 2019 Microsoft introduced service protection API limits to the Common Data Service on its Power Platform. Customers using TIBCO Cloud™ Integration - Connect, TIBCO Scribe® Online, and TIBCO Scribe® Insight to connect with Dynamics 365 CE/CRM cloud applications or the Common Data Service might encounter these API limits.
The total number of API requests is limited by each user, per organization instance, within a five-minute sliding window. The number of concurrent requests is also limited. API calls made from plug-in code does not count against this external API request limit. See this article from Microsoft for more information about the nature of the API limits: (https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/api-limits).
It is recommended to read this post to become familiar with how the limits work and with the associated error messages. (https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations#microsoft-power-platform-requests-allocations-based-on-licenses).
These licensing changes are scheduled to be enforced/metered after a transition period on October 1, 2020, or the expiration of your current Office 365 subscription term, whichever is longer: (https://docs.microsoft.com/en-us/power-platform/admin/powerapps-flow-licensing-faq#how-does-the-change-to-powerapps-and-microsoft-flow-use-rights-for-office-365-applications-affect-me-will-my-existing-powerapps-applications-and-microsoft-flow-workflows-continue-to-work).
When one of these limits is exceeded, an exception will be thrown by Dynamics 365 CE/CRM.
If you have any questions regarding your user or tenant API request limits/allocations within D365 CE/CRM, please open a ticket with Microsoft Support.
Affected Users
TIBCO Cloud™ Integration, TIBCO Scribe® Online, and TIBCO Scribe® Insight users may see error messages generated from the existing API limits/allocations: (https://docs.microsoft.com/en-us/dynamics365/customer-engagement/developer/api-limits#what-happens-when-the-limit-is-exceeded).
Many other connectors work with APIs that enforce API rate limits. These errors are generally shown as row errors or fatal errors in your Execution History and Agent logs.
To reduce the number of transient errors that could interrupt data processing, TIBCO has upgraded its TIBCO Scribe® Online connectors for Microsoft D365 CRM/CE and Microsoft Common Data Service and the corresponding TIBCO Scribe® Insight adapter to perform retry logic when the error response from the service specifies the amount of time to wait before sending more requests. The initial instances of these errors will not be reported by the connectors or adapter, but instead will be handled automatically. For TIBCO Cloud™ Integration and TIBCO Scribe® Online, the retries will be recorded in agent logs. After 3 retries, the connectors will stop retrying and the error from Microsoft will be passed through and will be visible in Execution History. For TIBCO Scribe® Insight users, the adapter follows the same retry logic and after 3 retries the error will be visible in the Execution Log.
The update for TIBCO Scribe® Insight is available as TIBCO Scribe® Insight Adapter for Microsoft Dynamics 365 And CRM 5.6.2 hotfix 5. See this article for information about the hotfix.
https://support.tibco.com/s/article/TIBCO-Scribe-Insight-Adapter-for-Microsoft-Dynamics-365-And-CRM-5-6-2-hotfix-5-is-now-available
Some users may still encounter limits or allocations based on integration design. There are configuration settings in TIBCO Scribe® Connectors/Adapters to help reduce the number of API hits, such as the Maximum Batch Size and Maximum Batch Threads settings on your connection configuration.
Best Practices
Many users can resolve limit/allocation errors and/or prepare for rate limit licensing enforcement by using existing connector features to help mitigate excessive API usage. Review the following TIBCO Scribe® features as you (re)design integrations with D365 CE/CRM:
- Batch Processing - Ensure that target operations make use of batch processing when possible.
- Upsert and Alternate Keys - Avoid excessive Lookups or Update/Insert blocks by defining Upsert operations and defining Alternate Keys.
- SkipSeekUnder - Avoid unneeded lookups that prepare target operations (such as Update) by using the SkipSeekUnder feature.
- Reprocess Rows - Transient errors such as these can easily be reprocessed when more API hits are available.
- https://help.scribesoft.com/v2/en/index.htm#conn/crm.htm
- https://help.scribesoft.com/v2/en/index.htm#conn/cds.htm
- https://help.scribesoft.com/scribeinsight/en/index.htm#Subsystems/AdapterForDynamicsCRM/boilerplate/welcome.htm
Timeline
- Request limits and allocations - live now
- API limit-based licensing - October 2019
- Update to the TIBCO Scribe Online Connectors for Microsoft Dynamics 365/ CRM and Microsoft Common Data Service - live now
- Update to the TIBCO Scribe® Insight Adapters for Microsoft Dynamics 365 / CRM - Hotfix available now
- API limit enforcement/metering - beginning October 2020 with rolling enforcement based on when your subscription ends
Issue/Introduction
Microsoft introduced API limits to its D365 CE/CRM cloud application earlier in 2019.
Feedback
Yes
No
Powered by
