Skip to main content

Part 5: Sitecore Dynamic CRM Connector: Sync Custom Facets(Checkbox Field)

Part 5: Sitecore Dynamic CRM Connector: Sync Custom Facets(Checkbox Field) 



In this blog, we are going to sync custom facets from Sitecore to CRM. The custom facets document is available here so I am assuming that you have already created custom facets. 

  • Go to this location "/sitecore/system/Settings/Data Exchange/Providers/xConnect/Collection Models" and create a new "Collection Model Folder".
  • Inside this folder create a "Compiled Collection Model" and type the namespace and assembly name of your custom facet model in the "Collection Model Type" field.


  • Go to this location "/sitecore/system/Data Exchange/<Tenant Name>/Endpoints/Providers/xConnect/xConnect Client Endpoint" and in the Collection Model field select the custom model which you have created in the previous step.


  • Go to this location "/sitecore/system/Data Exchange/<Tenant Name>/Pipelines/xConnect Contacts to Dynamics Sync Pipelines/Read Contacts from xConnect Pipeline/Read Contacts from xConnect" and in "Contact Facets To Read" field select your custom facets.


  • Go to this location "/sitecore/system/Data Exchange/<Tenant Name>/Data Access/Value Accessor Sets/Providers/Dynamics/Dynamics Contact" and create a new item using the "Entity Attribute Value Accessor" and enter the CRM field name in the Attribute Name field.




  • Go to this location "/sitecore/system/Data Exchange/<Tenant Name>/Data Access/Accessor Sets/Providers/xConnect" and create a new item using "xConnect Entity Facet Value Accessor Set" template.

  • Inside this folder create the below item:
    • Template: /sitecore/templates/Data Exchange/Providers/xConnect/Data Access/Value Accessors/xConnect Entity Facet Property Value Accessor
    • Name: IsSubscriber on Custom Facet in XConnect Contact



  • Now set "Facet Property".



  • Move to this location now "/sitecore/system/Data Exchange/<Tenant Name>/Value Mapping Sets/xConnect Contact to Dynamics Contact Mappings/Contact Model to Dynamics Contact" and create a new Value Mapping item. Now select Source Accessor and Target Accessor.

  • In the last step, go to this location "/sitecore/system/Data Exchange/<Tenant Name>/Pipeline Batches/xConnect Contacts to Dynamics Sync" and run the pipeline. 
You can go to CRM and verify checkbox must be synced.

Enjoyyyyyyyy!!!!!!!!!


Labels:

Comments

Post a Comment

Popular posts from this blog

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine’” on Windows 11

Sitecore 10.2 - “Failed to start service ‘Sitecore Marketing Automation Engine' ” on Windows 11 Today I started to install Sitecore 10.2 using Sitecore Instance Manager on Windows 11 and I got this issue “Failed to start service ‘Sitecore Marketing Automation Engine' ” . Error : On event viewer it was showing the below error: I also tried to run ‘ Sitecore.MAEngine.exe ’ like this C:\Windows\system32>C:\inetpub\wwwroot\sclocal102xconnect.dev.local\App_Data\jobs\continuous\AutomationEngine\Sitecore.MAEngine.exe Which was throwing below error: Starting Marketing Automation Engine... 2022-01-29 22:21:11 ERR Error initializing XConnect client. System.AggregateException: One or more errors occurred. ---> Sitecore.XConnect.XdbCollectionUnavailableException: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected err...
Post a Comment
Read more

Sitecore Custom API Issue with Federation Authentication

Sitecore Custom API Issue with Federation Authentication In earlier segments, detailed in Part 1 and Part 2 of the blogs on Keycloak Integration with Sitecore, I introduced Keycloak functionality for CM login. Concurrently, I addressed a necessity to develop custom APIs for retrieving Sitecore users and roles. Following the development of custom APIs, during authentication failures, the API erroneously returned a status code of 200 instead of 401. The problem arose because API requests were being routed through the "owin.identityProviders" pipeline, which was not intended for API usage. Solution: When OWIN identifies a 401 response and the AuthenticationMode is set to "Active," it fails to capture the URL hash included in the request. Another choice is to activate the "Passive" AuthenticationMode, wherein OWIN refrains from actively intercepting 401 responses. In passive mode, your application needs to explicitly issue a Challenge to trigger the OWIN aut...
Post a Comment
Read more

Azure AD Integration with Sitecore 10.2

 Azure AD Integration with Sitecore 10.2 Sitecore identity server that comes with Sitecore 9.1 allows you to log in through an external identity provider like Azure Active Directory, Facebook, Apple, or Google. It is built on Federation Authentication. What is Federation Authentication? Federation authentication is a technology to allows users to access multiples application, tools, and domains using one credential. Using one set of credential user can access multiple applications, and resources after authentication.  Federation authentication consists of two systems, the Identity provider and the Service provider. Identity providers that maintain/create/manage identity information like name, email address, device, and location. Some examples of identity providers are Azure AD, Google, Facebook, and Apple. Service providers basically refer to a website, software, or app that the user is trying to access and SP basically relies on the identity provider to authenticate the user ...
Post a Comment
Read more