Skip to main content

Sitecore 9 Dynamic CRM Connector: Sync CRM field with Sitecore custom facets (Part 7)

Sitecore 9 Dynamic CRM Connector: Sync CRM field with Sitecore custom facets (Part 7)

In previous blog, we have discussed how to sync Sitecore custom facets to CRM.

Dynamic CRM Connector comes with out of box functionality to sync CRM with Default facets, but we are going to discuss how we can sync CRM with Sitecore custom facets.

Step 1: Specify how to read from the Dynamics contact

  • Navigate to this location “/sitecore/system/Data Exchange/XXX/Data Access/Value Accessor Sets/Providers/Dynamics/Dynamics Contact”
  • Add the following item:
    • Template: Entity Attribute Value Accessor
    • Item Name: GraduateYear on Dynamics Contact
  • Set the following field values:
    • Attribute Name: CRM Field Name
    • Value Type: Option Set Value (If dropdown, if checkbox select Formatted Value otherwise blank for single line)

Step 2: Specify how to write to the Contact facet

  • Navigate to this location “/sitecore/system/Data Exchange/XXX/Data Access/Value Accessor Sets/Providers/xConnect”
  • Add the following item:
    • Template: xConnect Entity Facet Value Accessor Set
    • Item Name: xConnect Contact Custom Information Facet
  • Select the new item.
  • Add the following item:
    • Template: xConnect Entity Facet Property Value Accessor 
    • Item Name: Graduate Year on xConnect Graduate Year
  • Set the following field values:
    • Facet Property: Collection Models > Custom Models > YourCustomModel > Facets > Contact > FacetKey > GraduateYear
  • Save the item.

Step 3: Map Dynamics data to the contact facet

  • Navigate to this location /sitecore/system/Data Exchange/XXX/Value Mapping Sets/Dynamics to xConnect Contact Mappings” 
  • Add the following item:
    • Template: Value Mapping Set
    • Item Name: Dynamics Contact to xConnect Contact Custom Facets
  • Add the following item
    • Template: Value Mapping
    • Item Name: Graduate Year
  • Set the following field values:
    • Source Accessor: /sitecore/system/Data Exchange/XXX/Data Access/Value Accessor Sets/Providers/Dynamics/Dynamics Contact/GraduateYear on Dynamics Contact
    • Target Accessor: Data Access/Value Accessor Sets/Providers/xConnect/xConnect  ; Contact Custom Information Facet/Graduate Year on xConnect Graduate Year

Step 4: Set xConnect Entity Facet Value 

  • Navigate to this location /sitecore/system/Data Exchange/XXX/Data Access/Value Accessor Sets/Providers/xConnect/xConnect Contact
  • Add the following item:
    • Template: xConnect Entity Facet Value Accessor
    • Item Name: Custom Facet on xConnect Contact
  • Set the following field values
    • Facet Definition: Collection Models/<YourModel>/Facets/Contact/<Name>
    • Mapping Set: /sitecore/system/Data Exchange/XXX/Value Mapping Sets/Dynamics to xConnect Contact Mappings/Dynamics Contact to xConnect Contact Custom Facets/

Step 5:  Dynamics CRM sync with Sitecore Custom facet

  • Move to this location “/sitecore/system/Data Exchange/XXX /Pipeline Batches/Dynamics Contacts to xConnect Sync” and click on “Run Pipeline Batch”
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

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 and provi
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