I have also faced similar issue and I fixed that by doing some investigation like below:
Check if the certificates are present and valid in the xconnect site. If it is invalid or expired, generate those and assign it to the site bindings.
Check if the xconnect site is accessible through HTTPS.
Delete the Non-SSL certificate from Root.
Check if the sitecore ...
Sitecore support advised:
The issue is a bug with reference number 439986.
As a workaround for the issue, please try adding the following section:
<add value="Default.aspx" />
in the "web.config" ...
I had faced the same issue during the installation of Sitecore 9.3. It was because the certificate already exists with the same Sitecore instance name in my machine.
I have followed the below steps to get rid of this:
Removed the certificates from my machine with the same instance name
Removed the Sitecore instance from the inetpub ...
That data is never supposed to be changed. It's what user entered in the form, plus a random guid for FormEntryId - it's a unique identifier of that particular form entry (the one you highlighted in your screenshot). Its value has no meaning - it's just a reference so form reports and user related form data can be generated properly. It's like ID of Sitecore ...
If you don't actually need performance counters enabled, you can shut the functionality off by finding all of the files called sc.PerformanceCounters.Initialize.xml in the XConnect web root and changing
First, you need to create the Custom Facet in xDB that will be saved in your shard0 or shard1 table. After that, you can perform operations on those custom facets. You can find below listed documentation for more understandings:
Create Custom Facet Model in Sitecore
Work with Custom Facet in Sitecore
A method CurrentTracker.Session.IdentifyAs() in Sitecore....