Himmat Singh Dulawat (3x Sitecore MVP)

While installing Sitecore 10.4, I encountered an error about the Authenticode issuer and SitecoreInstallFramework version. The error message is about Sitecore Install Framework conflicts. To investigate more about it and to check the version I executed the following command in PowerShell and I have SIF version 2.3: Get-Module SitecoreInstallFramework –ListAvailable As stated in this error Sitecore 10.4 version requires SIF version 2.4 and to install it Sitecore suggested in error that use the -SkipPublisherCheck parameter, so to install this, execute the following command: Install-Module SitecoreInstallFramework -SkipPublisherCheck -Force After execution if you get the following error: Then Execute the following command to register repositories and register as trusted. Register-PSRepository -Name SitecoreGallery -SourceLocation https://nuget.sitecore.com/resources/v2 Set-PSRepository -Name SitecoreGallery -InstallationPolicy Trusted

Sitecore Content Hub provides an Annotation feature, that you can use to review content, provide feedback and collaborate with others.  To mention a Content Hub user in an Annotation, Select the text in Content Entity, enter @ followed by a username, and select as many people as you want. When you mention a user, they receive an email with your comment and a link to the content entity. The issue is Sitecore Content Hub Provides a feature that you can mention the User but if there is a User group and you want any of them can review, approve, or take action on the entity so no such option we have in Sitecore to mention a User Group in an annotation.  I have checked with Sitecore and Sitecore submitted a feature request for the Content Hub product so that it can be considered for future versions of the product. To track the future status of this request, please use the reference number " FRM-2121 ". See the Sitecore documentation for How

In this blog post, I will discuss how to add a custom button on the Content Details page in the Sitecore Content Hub. To understand the use case of this feature, suppose you have a client requirement to perform any business logic on that particular entity for instance updating field values or applying auto-tagging, etc. 1. Go to the pages option from the Manage button in the top right corner of the Home page. 2. In the pages, search for the Content Details page: 3. On the Content Details page, locate the operations/entity operations, in the Header Zone (Right). By default, it can be disabled so enable it by system settings. 4. After that, it will be enabled, and click on the Operation/Entity Operations it navigates to the entity operation component. 5. We will add a new operation, click on the Add operation button on the top left and find the custom External Action. 6. Name it as per your requirement, I am naming it AI Tagging, to change the

Sitecore Content Hub provides a script editor feature to write custom scripts and perform our business logic. Depending on the type of script and use cases, we can trigger the script manually or automatically using triggers. 1. Script: Sitecore Content Hub offers the following Script types . To create a script in Sitecore Content you can refer to the blog post:  Execute Content Hub Script using Postman 2. Action: Sitecore content Hub offers Action to perform a specific task. Action can either triggered by the user or automatically run by trigger or via the API. To create an action, go to the Content Hub dashboard using the manage icon and click on the Action icon: It will open an Action page window, click on the add New Action icon: In the popup window, provide the Name and Label of the action, Type I am selecting Action Script, choose the script that we created earlier, and click save: Your action has been created: For another Action ty

Sitecore Content Hub provides a script editor feature to write custom scripts and perform our business logic. Depending on the type of script and use cases, we can trigger the script manually or automatically using triggers. In this blog post, I am explaining how to execute the script manually using Postman. To execute the script from Postman, you need the Script URL and X-Auth-Token. Go to the Content Hub dashboard using the manage icon and click on the Script icon: It will open a Scripts page window, click on add new script icon: In the popup window, provide the Name and Type of the script and click save, I am choosing Action type here: Search your script in the Script window and click on the script name, it will open the script editor to write a script: Click on the Edit icon write the custom script and save the changes button: Click on the Build button, it builds your scripts and lets you know about the build status in the build output whe

After execution of the Rebuild index on xDB app service I observed that in SOLR Cloud, the data is not reflected in the xdb_internal collection but is being updated in the xdb_rebuild_internal collection. I have checked the Application Insight and found the following exception: In regards to the Errno 50000: Sync token is no longer valid for [Contacts] table error, Rebuilding the xDB index in Solr  should fix it but regrettably, it could not fix my issue. Indeed, when rebuilding the xDB index, the rebuild collection will be updated, and you will need to swap the cores to ensure that the newly rebuilt core is active instead of the prior one. This is mentioned in the " Confirm rebuild " part of the documentation. Therefore, I tried swapping the core mentioned in the Sitecore documentation but unfortunately, it's not working and returning me the error: "Not supported in SolrCloud". I have gone through the SOLR guide documen

Honored to Receive the Sitecore Technology MVP Award for the Third Consecutive Year!. Getting the badge of Sitecore MVP the third time in a row particularly in Technology for me is one of them. My journey for Sitecore MVP begins in the Year 2019. I commenced with Sitecore Technology blogs , and actively participated in the Sitecore Stack Exchange Platform , Sitecore Slack Channel , and SUGCON public speaking. I am honored to be named Sitecore Technology MVP 2024 . I feel fortunate to be participating with a Sitecore Community, Technology, and Product. I am happy that my all efforts and contributions are recognized by Sitecore and the Community. My next focus for this year would be: Exploring more in Sitecore composable including Personalize and CDP, Content Hub, and XM Cloud. Continuing with sharing and helping others in the Sitecore Community. Participating in Sitecore MVP mentorship program. A big thanks to my family, colleagues,

After deploying the Sitecore application on Azure PaaS, I noticed that the physical log files are absent from our PROD CM app service. I can find log files on the day of deployment, but for the subsequent days, the log files are not present on the PROD CM app service. It appears that whenever I perform a deployment, the old worker process (w3wp) retains an exclusive lock on the log file while shutting down, simultaneously, a new w3wp process is created and attempts to access the same log file. Since the file cannot be used by both processes at the same time, the logging appenders for the new w3wp may not initialize correctly, resulting in no further logging. For better visibility and clarity, I have raised the concern to Sitecore over a support ticket. Solution: The behavior I reported was registered as a bug in the Sitecore bug-tracking system. The bug specifically affects the log file appender after an application pool recycle, which happens afte

If you are using the SOLR search provider, to rebuild the request command we need to build the xDB index using the command manually from the xDB app service in Sitecore XP. You can find more details here: Invoke the rebuild request command Upon execution command, you get the following output: The index rebuild process takes time to complete and the request rebuild command does not provide any information about the progress status. However, there are certain ways you can monitor the state of an ongoing rebuild process. To Monitor the Index Rebuild Process: SOLR Interface: You can do so by running the following query by navigating to the original xDB Solr core and go to the Query tab. On the Query tab, insert the above into "q" part and click "Execute Query". Once executed, we should be able to see the result as such. In this example, the rebuild state is at 5 (Ongoing) and it is at 95%.