Views:

Applies to Product - Dynamics 365 Finance
 

What’s happening?
Customers are experiencing errors related to OData connections when attempting to integrate data from various applications, including Workday and Dynamics 365 Finance and Operations. Specific symptoms include failure to load applets in add-ins, authentication errors, and throttling issues.
 

Reason:
The underlying causes of the OData connection issues include: - The OData service being unable to return necessary data to the add-in, leading to failures in loading applets. - Slow queries and potential throttling of OData requests, particularly when there are more than 10 unauthenticated calls to any OData endpoint within a specified time window.
 

Resolution:
To resolve the OData connection issues, the following troubleshooting steps should be taken: 1. For Add-in Loading Issues: - Ensure the user is signed in correctly. Sign out of the add-in and sign back in to resolve issues caused by using the wrong user context. - Verify that the environment has all add-in data initialized. Check the relevant tables (App parameters, Registered applets, Registered resources) and ensure they contain data. If any tab is empty, click the appropriate Initialize button. - If the above steps do not resolve this, check if the OData service is functioning correctly and returning data.

  1. For Throttling and Query Issues:
  2. Review the number of unauthenticated OData calls. Reduce these calls to fewer than 10 over a 300-second window.
  3. Consider moving to an authenticated metadata endpoint to avoid throttling issues.
  4. If slow queries are identified, optimize the SQL queries and consider adding indexes to improve performance.
  5. For Authentication Errors:
  6. Review the call method and ensure that the OData only returns data belonging to the user's default company. To access data from outside the default company, specify the ?cross-company=true query option.
  7. Check if the 'IsPublic' property has been marked as true for the concerned entity. If not, set it to true and retry accessing the data.
If the issue persists after following these steps, further investigation may be required to identify any additional underlying causes.