Daivagna Nanavati

Hi Fellas, In today's blog post I will share a scenario which will help you also in your implementation, what is important here is to understand the issue when it is produced. Generally, it is always puzzling why certain components show different results on different page refresh, and because my team members also spent same amount of time on both of the different scenarios and hence, I thought to get this article out, I will explain those two scenarios and also provide solution at the end, Though solution is easy and available on lot of sites but important here is finding out what is the issue and what are the steps to identify it, so in this blog post my focus is to show you the steps of identification rather than solution. Scenario Here are those two scenarios Sccenario-1 On a home page we have a Sitecore component, which has a custom resolver, and that resolver basically reads from solr index and hits the query and returns the JSON result, and that is being read in JSS component

Hi Team, Today's blog post is regarding real live scenario which we came across while having multisite solution in Sitecore headless set up. Well, We have had couple of deployments but one fine morning after the deployment we started getting below error on our stagging site (UAT) and in Sitecore logs we were getting same following logs  Exception: System.InvalidOperationException Message: Unexpected provider type: System.String. Expected: Sitecore.Links.LinkProvider Source: Sitecore.Kernel    at Sitecore.Configuration.DefaultFactory.GetProviders[TProvider,TCollection](List`1 nodes)    at Sitecore.Configuration.DefaultFactory.GetProviders[TProvider,TCollection](String rootPath, TProvider& defaultProvider)    at Sitecore.Configuration.ProviderHelper`2.ReadProviders()    at Sitecore.Configuration.ProviderHelper`2.get_Provider()    at Sitecore.Links.DefaultLinkManager.ParseRequestUrl(HttpRequest request)    at Sitecore.Web.RequestUrl.Parse(HttpRequestBase request)    at Sitecore.Pi

Hi Team, I had an opportunity to take part in " Collaborative Program – XMC Forms Early Access" with Sitecore team to play around XM Cloud Sitecore Forms along with few of my colleagues before 6 months, When forms were not released officially, and the purpose was to review XM Cloud forms and provide feedback around it, We had great opportunity to connect with product Strategist  Christa Marousek  and Senior Product Manager  Marina Kostopoulou  on reoccurring meetings. I along with my colleagues  Brijesh Patel    Nimit Patel   Varun Shringarpure    Jatin Prajapati   Varalakshmi MD   Gautam Bulchandani   Irfan Masurkar  and lot other folks explored Sitecore XMC Form and provided our inputs / feedbacks / improvement that we think should be part of public offering of Sitecore XMC Forms. The objective of that program was to get inputs from partner community about forms and give them a feedback and improvise it. In this blog i will highlight what feedback as a team we gave to Sitec

HI Team, This one will be very quick blog post, But sharing it here so it helps anyone on the internet having same issue Problem We are using SearchStax and we have been using auto suggestions functionality of it, Everything was working fine and suddenly lot of users started reporting that they are not able to search anything in the search box. As this was P1, I started looking into the probable cause and logs, first i saw in console that we were getting 500 error, that means there is some issue being thrown from the backend. Upon checking logs found following in logs  The error was "suggester was not built" Well, I knew there is some issue with suggester which causing it to fail, but puzzle was, It has always been working for us Now, because we have this error on SearchStax documentation, If you refer below link, it says  https://www.searchstax.com/docs/hc/suggester-was-not-built/ "The root cause is often query fields that are not defined in the Solr schema. Look in the

Hi Readers, I want to talk to you about interesting things which we have been doing which is "Technical Workshops" for our customers, so here goes the scenarios. So, we have been doing multiple types of technical workshops.  1) Training customer and their Sitecore technical team on latest and the greatest technologies like XM Cloud & Another composable stack and try enabling them for new Sitecore tech stack. 2) Customers / Potential Customers have their agenda of existing pain points, and we take a workshop on topics around them with best practices etc. little on new technologies, so they also know the future. Basically, we prepare custom targeted presentations & demos for individual workshops, and make sure it helps them answer their questions and they get insights of where Sitecore eco systems has to offer from their versatile toolset and try to keep them up to date with it. So, Purpose of this blog is, because in all these customer & their technical team's

Hi Team, Recently, I faced an issue where for the new project my Sitecore serialization started giving me following error. Error: "Error connecting to https://sc10.dev.local/.well-known/openid-configuration: Bad Gateway" My identity server when browsed above url was also not working and showing following. Well, I tried seeing logs and different things, I also followed what is given on these links.  https://sitecore.stackexchange.com/questions/34744/open-id-configuration-issue-with-sitecore-cli https://tekkishare.azurewebsites.net/pages/sitecore-clilogin-error-badgateway https://www.stockpick.nl/english/sitecore-cli-login-error/ But I was still getting the same error. Solution If you see above screenshot of my identity server, in "Troubleshooting steps" it is mentioned that "Check the system event log for error messages." It triggered me, I opened event log of windows, and I could see following error.  Now, i already update my .net run time version accordin

Hi People, First of all congratulations to all 2024 MVPs, Last year has been a community year where we saw lot of new MVPs and lot of new content coming from lot of people, Good learnings. I wanted to share some articles on the real discoveries and headless implementation we did and journey we had and what all things were involved in it etc. but i will bring that later on. Today i am going to talk about "Component Builder", Amazing tool of Sitecore XM Cloud, Last year i did lot of research and hands on to "XM Cloud Component Builder", Very powerful futuristic tooling provided by Sitecore. At that time it was still in "Early Access" phase, but now the offering is fully available, i wanted to revisit and provide almost all the info related to it and will also show, How to create fully functional website without writing any code, yes " It is low code / no code ". Last year i presented at SUGCON-2023-India on "FeaaS - Front End As A Service"

Hi Sitecorians, It has been amazing learning year so far and with the change in technology and shift of the focus on frontend frameworks and composable products, it has been market demand to keep learning and exploring new things. Reasons behind this blog Today's topic is something that was in my draft from April-May, and I always thought that there is already a good documentation out there for  Leprechaun  and a blog post is not needed, Until I realized that there was so many of us facing same kind of issues and same kind of problems and spending same amount of time, That is where I thought, if I could write something which can reduce that repetitive troubleshooting time, That would really help the community. 1)  In a project environment, if we get into some configuration issues, we resolve them, we make sure we are not blocked and continue, but if you think same issue, same step and same scenario will come to other people, so if we can draft it online, it will help other people 2