8

I can suggest the following solution: You need to implement a custom field reader with a custom field converter: using Sitecore.DataExchange.DataAccess; namespace Example { public interface IBaseValueReader: IValueReader { string AttributeName { get; set; } } } AddressFieldReader: using System; using Sitecore.DataExchange.DataAccess;...


6

Go for Sitecore Forms. WFFM is no longer included in 9.1 so that is a dead end... You will need to create your own submit actions (in both options btw) if you want it on this version.. If you can wait just a little longer until the actual release of Sitecore 9.1 (announced for November) you will get an ootb data prefill framework in Sitecore Forms but that ...


6

In order for Sitecore to be able to access account information from CRM, the CRM user used to connect to CRM must have the following permissions assigned: Read account entities If these permissions are not assigned, an error will occur when Sitecore tries to read data from CRM.


5

I have figured a way: On the Read Contacts from Dynamics Pipeline there is a field "Filter Expression". If I create my custom condition "Where contact is my Test User" with one string condition inside to check the contact id - I can include that into the pipeline. Worked for me.


5

Unfortunately Dynamics CRM cannot send request to Sitecore to notify that entity was deleted. You can add a custom solution like "Clean Up Sync" pipeline batch to send a request to determine whether Dynamics Crm Entity exists by Sitecore record Id, if no remove record. Option 1 Read Sitecore Records Pipeline: Get All Sitecore Records Step Iterate Step -> [...


4

In order to get customer id you have to change your accessor template to It should be something like this And if the value Guid type you can use transformer Guid to String.


4

It's not clear to me exactly what you are trying to do, but it sounds like you ran a process to read data from CRM and write that data to Sitecore. Some of that data no longer exists in CRM, so you want to remove the data from Sitecore in order to keep CRM and Sitecore in sync. If this is what you want to accomplish, the first thing you need to do is to ...


4

Yes, you can simply do that. If you use a default Dynamics CRM Connector pipeline to sync contacts to CRM, you only need to navigate Pipelines -> xConnect Contacts to Dynamics Sync Pipelines(1) folder, expand Process Single Contact from xConnect Pipeline (2) item and choose the Resolve Dynamics Contact by Identifier (3). Then you can find the Entity Name ...


3

What Gert said is 100% valid. If you don't have to save in dynamics CRM in real time you can use Dynamics CRM Connect Module. After you create contacts in XDB you can use Dynamics CRM Connector to syncronize from xDB to Dynamics CRM. Dynamics CRM Connector has pipeline batches to sync XDB Contacts -----> CRM Contacts CRM Contacts -----> XDB Contacts ...


3

I am explaining custom facet Graduate Year drop down. Please follow below steps: Specify how to read from the Dynamics contact Navigate to this location Navigate to this location /sitecore/system/Data Exchange/XXX/Data Access/Value Accessor Add item GraduateYear on Dynamics Contact using template Entity Attribute Value Accessor Set the following field ...


3

Problem Solved Solution: If you are using just Sitecore CRM Provider, you should use "authentication type=2", if you are using Microsoft.Xrm.dl then you should use authtype=Office365, if you are using both dlls on the project (since they do different stuff), you can use "authentication type=2;authtype=Office365" Sitecore helped me on this issue (on the ...


2

Maybe it is not the most elegant solution, but you can try. First of all you need to create a new pipeline step template which is inherited from Resolve Contact by Identifier from xConnect Pipeline Step template. Let's call it Extended Resolve Contact by Identifier from xConnect Pipeline Step. Add three extra fields to the identifier section: ...


2

You missed 2 pipeline steps. Create Entity Queue - before add an entity to a queue you need to create queue. Submit Remaining Entities From Queue - checks if there are some entities in the queue after iterating and submit all of them. Add Entity to Queue Pipeline Step - adds entity to the queue but also can submit entities if its count in the queue ...


2

I see a few wrong thing in your implementation. Resolve Dynamics Contact By Identifier pipeline step: Identifier Value Accessor - This value accessor shoud be set for xConnect Contact, e.g.: Data Access/Value Accessor Sets/Providers/xConnect/DynamicsContact/TrainingId. This value accessor is used to get identificator for resolving entity in Dynamics CRM. ...


2

Rebuild the Databases and Indexes, this will fix the issue. It worked for me.


2

Wrote a custom rule referring to default null mapping rule, and applied on specific value mapping. This solved my objective


1

This issue has been resolved after rebuild xConnect using below command: C:\inetpub\wwwroot\XXX.xconnect\App_data\jobs\continuous\IndexWorker> XConnectSearchIndexer -rr


1

Yes this is a normal behavior. Your contacts are anonymous (without interactions) and anonymous contact are not indexed OOTB. To change the contact to be indexed you need to change in 2 places in xconnect: Open the xConnect Search Indexer's sc.Xdb.Collection.IndexerSettings.xml configuration file. In a default on-premise deployment, the full path is C:\...


1

Sitecore.Xdb.Common.Web.IHttpClientHandlerModifier doesn`t exist in Sitecore 9.0.2 (only in Sitecore 9.1). As I know Microsoft Dynamics 2.1.0 requires Sitecore 9.1 version. You can check sitecore modules compability here https://kb.sitecore.net/articles/541788.


1

The pipeline is trying to set the marketing list property to null. By default, a null value will not overwrite an existing value. To change this: Open the Content Editor Select your tenant Navigate to Value Mapping Sets > Clear CRM List Membership on xDB Contact > Marketing Lists Untick the field Ignore null values Save the item


Only top voted, non community-wiki answers of a minimum length are eligible