New answers tagged

0

xConnect Search Indexer will either be a Windows Service or Azure WebJob. So, I believe the server in which this service or job is configured should be able to cope up with the processing load - which will be based on the number of visitors that come to your website. As the index grows in Solr / Azure Cognitive Search, there is also a growth in the server ...


3

We faced this issue while upgrading as well, so we noticed that some configurations need to be changed like in above @Marek answer you can see droplink|droptree returnType is stringCollection instead it should be string, if you change it index again then you will notice now droplink field will come as _s in solr indexing. So changed these as below - <...


1

You should check your SolrIndexConfiguration in /sitecore/admin/showconfig.aspx. There should be entries for every type of the field and their corresponding type in Solr: <defaultSolrIndexConfiguration type="Sitecore.ContentSearch.SolrProvider.SolrIndexConfiguration, Sitecore.ContentSearch.SolrProvider"> <fieldMap type="Sitecore....


1

Looks like the connection string for solr core xdb is wrong or the solr core xdb doesn't exist/is not configured correctly. Can you check if your connection string on xconnect looks like : <add name="solrCore" connectionString="https://yoursolrdomain:port/solr/XP0_xdb" /> and you can access the core? https://yoursolrdomain:port/...


Top 50 recent answers are included