Dynamics 365 FO integration using https vs finance connectors
Poojith Jain
50
Like
Share
ReportHTTPS vs D365UOconnectors for integration with D365UO
Microsoft Dynamics 365 for Unified Operation provides project-driven organizations with the tools they need to connect and manage their clients, finances, projects, and people in a unified, integrated environment. D365UO helps services organizations streamline key finance and project-related business processes, simplify the management of their human capital, and gain the visibility they need to maximize their revenue and profitability levels. Microsoft D365UO connectors provides following operations:
| ACTIONS | |
| Create record | Create a new record in an entity |
| Delete record | Deletes a single record in an entity |
| Execute action | Execute action |
| Get a record | Retrieves a single record |
| Get list of entities | Retrieves a list of entities |
| Lists items present in table | Lists items present in table |
| Update a record | Updates a single record in an entity |
The Microsoft Dynamics 365 for Finance and Operations connector uses the OData version 4.0 protocol. The connector has following limitations
- It does not support cross company queries
- This connector does not currently have built-in proxy support and does not honor the Atom proxy settings
So i have been using HTTPS connector to perform the CRUD operations on D365UO. The following table shows the reason to use the HTTPS connector instead of D365UO connector.
| HTTPS | Dynamics connector |
| Performance is much better (~8x faster). This because it makes a direct connection D365FO environment | Performance is poor. The call goes via custom connector, then to D365FO |
| It supports Cross company queries | It does not support cross company queries |
| Less probability throttling exception. The throttling exception is limited to D365FO | More probability throttling exception. The throttling exception is limited to D365FO |
| Supports App and Managed identity-based authentication (more secure) | It does not Supports App and Managed identity-based authentication (more secure) |
| Nesting of queries (Expand) is supported, resulting in lesser actions. As a result, cheaper and faster execution of Logic App | Nesting of queries (Expand) is not supported, resulting in lesser actions. As a result, expensive and slower execution of Logic App |
| No impact on Microsoft changes to dynamics connector | The integration could break due to changes done by Microsoft |
| The development time is higher and requires more technical skills. | This connector helps developer and reduce the development time |
This was originally posted here.
*This post is locked for comments