Himmat Singh Dulawat (3x Sitecore MVP)

After successfully installing Horizon on Virtual Machine and solving the Horizon issue due to the URL binding in the IIS. And everything is working perfectly fine. Now it turns to Horizon URL binding and I have bound with a new URL name i.e., horizon.abc.com.  I opened the new Horizon URL in the browser and wait there is a new error I am getting, and it is related to the Authoring and SSL. If you want to install Horizon and facing some pre-post installation issues and looking for fixes, then my previous blogs can help you. Install Horizon 10.2 with Sitecore XM Sitecore Horizon Issue Pre and Post installation Issue 1: When I hit the horizon.abc.com in the browser, it’s redirecting me to the identity server URL for authentication and but after entering the credential it does not redirect me to the Horizon page. Solution: Go to the Sitecore Identity Server instance and open Sitecore.IdentityServer.Host.xml file {root directory}\ sc10

In my previous blog , I discussed with you the installation of Sitecore Horizon in Sitecore Experience Manager. In the continuation of this blog, I am going to discuss some common issues which I have faced while installing Horizon and after installation. Issue 1:  Authenticating Error This is the issue I have faced while installing Horizon on Virtual Machine. The reason behind the issue was we have done binding on the Sitecore instance URL and changed the URL name to expose it outside the VM. Example: My instance name was sc102xmcm.local and sc102xmidentityserver.local and we have updated the binding of the URL in IIS with cm.abc.com and identity.abc.com. Solution: To solve the issue you need to take care of the following highlighted parameter value in the InstallHorizon.ps1 file. Issue 2 : Search/Indexing issue: If your search in Horizon is not working. Solution: It is because the $solrCorePrefix parameter value you assigned in InstallHor

There are plenty of documents and blogs available on installing Horizon with Sitecore XP Experience Platform  but this blog is related with install Sitecore Horizon with Sitecore XM Experience Manager . Horizon is the next-generation editor in the Sitecore Experience Platform. Horizon comprises two editing tools where you can create and edit content. Before installing Horizon, you need to install the below prerequisites for Sitecore 10.2: Install Sitecore Experience Manager 10.2 Make sure your Sitecore CM site is working correctly with the HTTPS protocol. Ensure Sitecore Identity is installed Install WebSocket Protocol installed in IIS If you are on a local developer machine: Go to the Turn Windows Feature on or off from the Programs and Features option in Control Panel. If you are on Virtual Machine: Go to Server Manager, and select the Add roles and feature option in the right

After upgrading the Sitecore version 9.0.2 to version 10.2. I faced one more issue related to the Forms that is I am not able to see any forms and its shows a message there are no forms to display. I have checked the console and logs as well but regrettably did not find any relevant error. I have checked the Forms node in the Sitecore content tree and all forms were there. Solution: Cleared browser cache Cleared Sitecore cache /sitecore/admin/cache.aspx Incognito/private mode to see if able to see the Forms Rebuilt Forms folder from the Developer menu (It solved my issue and happy to see the Forms in Forms Designer) If step 4 does not help you then go to the Control Panel, and choose the Indexing Manager option. Once you click It will open an Indexing manager window then opt for the selected indexes and rebuild Result: If you still face the same issue then you can check the other possible case:

After upgrading the project to Sitecore version 10.2 , the SOLR search result is different in order due to the query _val_:__boost function . I have investigated the issue and found out that in Sitecore 9.0.2 our SOLR search query was: ..........AND (-_template:("083a4d2a38694013a9e2d18c05da70ae") *:*)) and in Sitecore 10.2 SOLR search query is: ..........AND (-_template:("083a4d2a38694013a9e2d18c05da70ae") *:*)) AND _val_:__boost There is one more extra condition at last in the query i.e. AND _val_:__boost. I have gone through the Sitecore documents on Search Result Boosting and found that  In Sitecore XP 10.0.0 or later, item-level boosting relies on index-time scoring factors that are indexed in the __boost field and combined with the query score using the query _val_:__boost function. After doing lots of brainstorming I raised a support ticket to the Sitecore and find the below solution: Solution: Sitecore suggested

While rebuilding the index on your Sitecore CMS you may face scenarios where indexing data not populating in website search functionality, search stopped working, or slowdown. After completion of indexing again search functionality returns the results. Here Sitecore introduces the very nice concept of SwitchOnRebuild. To understand it assume you have two cores for your Sitecore index active and passive. It means when you rebuild the Active index Sitecore will return the result using the Passive index and after rebuilding Sitecore will switch the Active index to serve the results. It’s a concept of switching of Sitecore index during the rebuild of the particular index to avoid downtime and search unavailability. Recently when I was working on one migration project, when I deployed an application on the Azure Paas environment. I faced a similar type of issue while rebuilding the index it was throwing me the below error: Job started: Index_Update_IndexNa

Sitecore Content Serialization is the development process, in which we move content changes between different environments. It allows us to pull, push, publish items and create packages for the various environment. With the release of Sitecore 10 came two new tools that support content serialization—the Sitecore Command Line Interface (CLI) and Sitecore for Visual Studio. In the Sitecore content Serialization using CLI developers need to configure modules, a set of rules to control what item you want to serialize and how you want to control the pull, push, and other option in your project. In the continuation of my previous blog on Sitecore Command Line Interface , in this blog, I am going to discuss with you Sitecore Content Sterilization using CLI. Install Sitecore Management Service: Sitecore Management Services is a package that you must download and install in your Sitecore Content Management (CM) instance to support Sitecore Command Line Inte

The Sitecore Command Line Interface is a new feature with Sitecore 10 and higher versions. It provides the ability to login into the remote Sitecore instance, serializes items, and publish, package, and additional commands reference for the command line. I have divided this blog post series into the below section: Configure Sitecore CLI on the workstation Sitecore Content Serialization with CLI Sitecore Content Serialization with Visual Studio You may have seen several blog posts, and videos on the same, but in this blog, I will make it easier for you and you do not need to set up the Sitecore project using Helix-base or getting a start template. In the first blog of the series, I will let you know about configuring Command Line Interface on the developer workstation. Once it will configure you can utilize another tool with Sitecore which is Content Serialization using CLI and Visual studio. Sitecore Command Line Interface (CLI) allows con

What is Docker? Let's say you created an application and it's working fine on your local machine, but in QA or Prod, it's not working properly. So, it's a common statement that it's working on my machine does not know why it's not working there😊. The reason can be libraries, version mismatch, framework, dependencies or you have upgraded any dependencies to solve the issue and forget, or any other reason and other developer machines and environments do not have all of these. Hence Docker Desktop is an easy-to-install application for your Mac or Windows environment that enables you to build and share containerized applications and microservices using containers. Docker is an open-source project for automating the deployment of applications as portable, self-sufficient containers that can run on the cloud or on-premises. In a container-based approach, the host operating system’s kernel and resources are directly shared by the con

After successful implementation of the Sitecore project, page performance comes into the picture in the context of page load time, slowness of page, or rendering. There are many tools available online to investigate the website performance like PageSpeed Insights, JMeter, GTmetrix, Lighthouse, etc., but Sitecore provides its own tool for troubleshooting the Sitecore performance issue i.e., Sitecore Debugger. “If you don’t have a fast website, users will bounce faster you can say. Google recommended page load time is under two seconds, However, speeding up your website is no easy task.”- Google This tool finds out the problems related to slow rendering, and pipeline time is taken and provides the other details for rendering like data source, parameter, Profile, cache setting, output, etc. The debugger facilitates developers to scrutinize the output of both the rendering and the entire page. So that developer can take care of page performance issues while