D365UO https vs finance connectors

HTTPS 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 recordCreate a new record in an entity
Delete recordDeletes a single record in an entity
Execute actionExecute action
Get a recordRetrieves a single record
Get list of entitiesRetrieves a list of entities
Lists items present in tableLists items present in table
Update a recordUpdates a single record in an entity
D365UO connector operations

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.

HTTPSDynamics connector
Performance is much better (~8x faster). This because it makes a direct connection D365FO environmentPerformance is poor. The call goes via custom connector, then to D365FO
It supports Cross company queriesIt does not support cross company queries
Less probability throttling exception. The throttling exception is limited to D365FOMore 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 AppNesting 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 connectorThe 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

Published by Poojith Jain

Poojith Jain is an Azure Architect with good experience with software design and development. He has a thorough knowledge of Azure Integration and he is passionate about solving complex and challenging problems in the field of Azure

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: