Wednesday , May 24 , 2017

SJSoftech's MSCRM BizTalk Adapter

 It`s fast, easy to integrate.

 

We are existed to announce the release of “SJ Softech’s BizTalk Adapter for MS Dynamics CRM 2011, 2013 & 2015” ver 3.0, which is now certified by Microsoft. This adapter will allow a seamless integration between BizTalk Server (ver 2009, 2010 & 2013 ) and Microsoft Dynamics CRM 2011, 2013 & 2015. Using this adapter, development and maintenance cost of BizTalk applications will be reduced by at least 50%.

  

Why do you need a separate BizTalk Adapter for integrating with MS Dynamics CRM ?

In MS Dynamics CRM 2011, 2013 & 2015, Microsoft provided a native WCF service which can be directly used in the Microsoft BizTalk Server. However, the use of this WCF service introduces lot of complexity in the BizTalk solutions. The creation of a service reference for this WCF service will result in adding too many entries in the BizTalk solution and most importantly the generated schemas are completely generic and independent from CRM entities. Due to the generic approach, the individual attributes of the entity do not appear in the schemas, instead the individual attributes are to be filled through key/value pair elements in the schema. Since the individual attributes of the entity are not available in the generated schemas, the BizTalk developer needs to know all the attributes and has to enter them into the appropriate functiods. This approach in BizTalk maps will increase the complexity of BizTalk solution and cost of maintaining such complex BizTalk solution will also increase with time.



Using the SJ Softech’s MS Dynamics CRM Adapter

Using our adapter, developer can generate very strongly typed schemas for the entities they want to integrate, instead of generating schemas for every entity in CRM. As the schemas are strongly typed, all entity attributes from CRM are created as xml nodes with appropriate data types. Moreover, without the need of two schemas – one for request and another for response, one schema per entity can be used for both request and response. This adapter allows the use of a special operation called “Upsert” (which does not exist in CRM) apart from regular CRUD operations. Our adapter has many more rich freatures which will allow BizTalk developers to developer a high quality integration solution in a very shorty period of time. The end solution is less complex and the cost involved in long term maintenance of the system will also be very less.



Refer to Features Tab for key features of the adapter.
null

Features

  Standard Edition  

  Enterprise Edition  

Process Single Entity

X

X

Process One To Many Relationship Entitie/s

 

X

Process Many To One Relationship Entitie/s

 

X

Insert Operation

 X

X

Update Operation

X

X

Delete Operation

X

X

Upsert Operation

 

X

Retrieve Operation 

X

X

User Key Condition Based Dynamic Lookups    

 

 X

Lookup Data Caching

 

X


Feature Details

Processing Single Entity

Process Single Entity feature is the standard and straight forward feature, where the adapter will perform standard CRUD operations on one or more individual entities without considering or traversing through their relationships. 

In the ER diagram, we have three entities where “account” is the parent of “contact” and “customeraddress”. This feature of the adapter will only be able to apply CRUD operations on “account”, “contact” and “customeraddress” separately.

Processing One To Many Relationship Entities

This feature of the adapter will allow performing CRUD operation on the parent and its immediate related entities in one call to the adapter without the need of any custom, complex BizTalk orchestrations.

Based on the relationship in ER diagram, this feature of the adapter can perform below functionality in one call to the adapter. Only thing a developer has to do is to map the data to appropriate entities and its attributes. It’s that simple.

a) create a new record in account entity,
b) create a new record in contact entity and establish a relationship with account record
c) create a new record in customeraddress entity and establish a relationship with account record.

Processing Many To One Relationship Entities

 

Insert Operation

Insert Operation will enable creation of new records in MS CRM entity or entities. This method will not check if a record exists or not before inserting a new record in entities. BizTalk developers have to write custom login to check if the record exist or not. Otherwise this operation will potentially create duplicates in CRM entities.

Update Operation

Update Operation will update an existing record in MS CRM entity or entities. This operation requires the primary key value (GUID in MS CRM) of the entity to perform a successful update of a record in MS CRM. If a matching record does not exist for the given primary key value in the MS CRM entity, update will fail.

Delete Operation

Delete Operation will delete an existing record in MS CRM entity or entities. This operation also requires the primary key value (GUID in MS CRM) of the entity to perform a successful deletion of a record in MS CRM. If a matching record does not exist for the given primary key value in the MS CRM entity, delete will fail.

Retrieve Operation

Retrieve Operation will retrieve the complete entity record based on the primary key (GUID in MS CRM) of the entity.

Upsert Operation

Upsert Operation will perform either an Insert or an Update on CRM entities. Unlike Insert and Update operations, this operation will check if a record exists or not in the entities based on the user key provided by the user in the xml messages. This operation will perform an update on the record if a matching record is found otherwise a new record is created. This operation will potentially reduce the custom code required to do additional check for the record existence.

User Key Condition Based Dynamic Lookups

Lookups are common in any integration projects where source system ids or codes needs to be translated or corresponding matching records in target systems needs to identified based on the target system ids or code and sent to the target system. This specific task itself usually requires substantial amount of custom code in BizTalk solution.

Using the “User Key Condition Based Dynamic Lookups” feature of the adapter, BizTalk developers can specify the user key condition on the xsd schema elements in BizTalk maps with which the specific information can be retrieved by the adapter while processing the message.  As the lookup data will not change quite often, adapter will cache the information retrieved and will reuse it in subsequent lookup data requests without making a round trip call to Dynamics CRM.

Lookup Data Caching

This feature will enable the caching of lookup data as it is being retrieved from Dynamics CRM. As the lookup data will not change quite often, adapter will cache the information retrieved and will reuse it in subsequent lookup data requests without making a round trip call to Dynamics CRM.

 

Please fill up the below form to receive an email with trail version download details. During the 15 days trail period all features of the adapter will work.

 

*
*
*
*
*
*
*
*
*
Captcha:

Are you interested in a Demo of the adapter features ? Do you need help with your CRM 2011 BizTalk integration work ?  Use the below form to write to us and we will be glad to help you.

 

*
*
*
*
*
*
*
*
*
Captcha:

For Installation Issues

For any type of adapter installation issues you can contact us either by filling the below support form or email us at adapter-support@sjsoftech.com or call us at 613 843 8930. We are not going to charge for any type of installation support requests. Depending on the nature of the issue we will get back to you as soon as possible.

For Adapter usage and Implementation related questions

For question related to adapter usage, functionality of adapter and adapter implementation, either fill the below support form or write to us at adapter-support@sjsoftech.com.


 

 

*
*
*
*
*
*
*
Captcha: