You need to add user interaction (either event or goal) before submitting the contact to XDB. I have Updated your first variant code as below:
public virtual ContactIdentifier CreateContact(string email, PersonalInformation personalInfo)
var identifier = new ContactIdentifier(ContactSource, email, ContactIdentifierType.Known);
In case this error persists, even after you rebuild the XDB index, you might as well want to check the items under /sitecore/system/List Manager/ListOperations node.
These items are created by the List Manager application and they contain a field named Sync Token. You should update the Sync Token field of each item with the one corresponding to your local ...
I would recommends you create a new environment and migrate your data/site into that environment. With 9.1 beyond xConnect you have identity server all all the configs that tie it together.
This file will set up all the parameters for xconnect install. Just change the name and paths to what you need.
I also had this same problem. The trickiest part is figuring out which application is having the problem because the only information you get in Application Insights is xConnect for the application name.
It took me some time to figure out which role was having the problem, especially because Sitecore in Azure PaaS is somewhat new to me. Once I figured out ...
There can be only one
If I misunderstood the above statement and you actually have 3 completely separate xDB collection databases, then you might be having a harder time as that is not a supported scaling model for the xDB database in 9.0 and 9.1
Here is the horizontal scaling documentation: https://doc.sitecore.com/developers/90/platform-administration-...
It's possible to create facets containing Dictionary<K,V> or List<T> properties in 9.1. Facet class needs to derive from Sitecore.XConnect.Facet. See Sitecore's documentation for more information.
Here's a sample facet class taken from XConnect's core model:
public class AddressList : Sitecore....
This sounds like the Marketing Automation Engine webjob is not running properly. This is an executable that, in Azure Paas, runs as a webjob in the MAops app service (for XP Scaled topologies) and responsible for enrolling contacts in plans and activities.
You can confirm it's running status in the webjobs blade in Azure portal. You can also restart it ...
The best guidance from Sitecore that is available for Disaster Recovery scenarios at time of writing is Sitecore Managed Cloud Standard — Disaster Recovery.
Notes of interest from the article:
xConnect Search Indexer
Sitecore can only have one active xConnect Search Indexer WebJob across a solution. In case of any failover and restore of service, ...
You also need to add at least one Interaction like goal or page view event. Below are the code:
using (var client = this.CreateClient())
//Set your facets here
Guid channelId = Guid.Parse(ChannelId);
string userAgent = "Form Update Contact";
Please check the below things.
1- Check the connection string on ServerB and check "xconnect.collection.certificate" has the same thumbprint that you have for Xconnect certificate on ServerA.
2- Make sure your server certificate (SSL) for XConnect is valid and can be validated from ServerB.
3- run MMC and check that certificate is exist in your local ...
You can follow this document https://www.codinglittlethings.com/2019/06/sitecore-9-dynamic-crm-connector-create.html and https://www.codinglittlethings.com/2019/06/sitecore-9-dynamic-crm-connector-sync.html
Tracker.Current.Session.IdentifyAs() will only merge contacts if the current contact is not a known contact yet: Contact.IdentificationLevel != ContactIdentificationLevel.Known
If the current contact already is known, IdentifyAs() will not merge it with an existing contact that already has the identifier.
So what we ended up doing was this:
public bool ...