Himmat Singh Dulawat (3x Sitecore MVP)

One of the frequent challenges we face is the absence of Analytics data in the Sitecore Experience Profile. This issue can be quite frustrating, but there is a solution. In this blog post, I will delve into the reasons behind the "The certificate was not found" problem and explain how to resolve it using Azure Managed Cloud Service PaaS. In this case, The very first step is analyzing logs on the CD and xConnect server. I have checked the xConnect Collection server's log and it seemed to stop, which suggested that there had been some issue with xConnect trying to collect the analytics data. In this case, I have to look into the CD server. I found a lot of xDB-related errors in the CD server, with a similar stack trace as below. Error: xDB unavailable when submitting contact The nested error seems to suggest the error is related to the missing client certificate required for xConnect and xDB communication. The amount of Submit Qu

The Add New Member option is missing from the Schema page. I have been investigating one of the issues in our Content Hub environment. I tried to recall the steps when I encountered a similar issue, but it resolved itself automatically after some time. Here are the steps I performed: Go to the M.content schema using the Schema option from the dashboard. Select the Settings option from the three-dot menu at the top right corner. Enable the Taxonomy-enabled definition. After enabling this option, the Add new member button disappears, along with the Settings option, making it impossible to disable the setting again. The above screenshot I have taken from different CH environments to elaborate on the issue. Workaround: 1. As a preliminary step, I recommend that you try discarding any changes to the M.Content schema. After doing so, verify if the new members become visible. 2. If it's still not resolved, then this issue belongs to the C