Himmat Singh Dulawat (3x Sitecore MVP)

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...