Daivagna Nanavati

Hi Team,  Recently i worked on one migration project where app was alrady live and working on 10.2 JSS, but it was supposed to be migrated over to 10.3 headless SXA. Team already did everything and migrated things, and it was working just fine apart from couple of things, one of them and most difficult error we were getting was below   "Placeholder "sxa-header" was not found in the current rendering data" Because of above no components were getting rendered Following steps i did initially to look into the behavior of this error 1) Checked all placeholders on next app side as well as on sitecore side, all looked ok 2) Double checked that headless layout has those placeholder in allowed place holder lists  3) Double checked that my layoutserviceconfiguration is targeting "sxa-jss" configuration and not "jss" because we did not run jss set up command, its all was looking good and it was working fine for "headless-header. headless-main, headles...

Hi Team, We all have been using Code Generators like Glass Mapper for our applications, Today in this post we will see the error which comes when you run leprechaun against XM Cloud starter repository, Steps for setting up leprechaun which are universal step & there is nothing major and very well documented at Leprechaun , So we will not discuss those step, You can easily configure it from the leprehaun site. Leprechaun is a universal, open API for code generation from Rainbow serialized or Sitecore serialized Sitecore templates. Leprechaun uses state-of-the-art Roslyn code generation technology instead of T4 templates for speedy generation that doesn't require Visual Studio. (Taken from https://github.com/blipson89/Leprechaun) Leprechaun is very well documented, so i will not talk much about it  But i will share some info where we were blocked for more than a week for which there was nothing available on the internet and those information i will share so you do not end up i...

Hi Team, Recently, While working on XM Cloud, I ran into wired issue, I did create multiple sites and create templates inside templates->Project-><<my sites folder>> Now i wanted to now start creating pages from those templates, so i right clicked on my home item of the site and selected "insert from template" option so i can select my "Blog Folder" template and can start creating my Blog items inside it, But with my surprise, it was not showing my site folder at all and i was puzzled as to how do i select my template and why it is not showing those folder? and surprisingly other site which i have it was showing it fine My template->Project folder actually had those site folders and templates inside it Solution I just compared both folder's template and with my surprise the one which was showing fine i.e "TrainingLab" had " /sitecore/templates/System/Templates/Template Folder " and the other site which was not showing had...

Hi Team, If you are exploring and working on XM Cloud and have set up XM Cloud instance on your local environment, You might run into following issue on publish   Because Sitecore XM Cloud instance works on Experience edge and there is no content delivery server which reads from WEB DB, It always publishes on experience edge Because we are habitual (at-least i am) to publish the API KEY after creation, Because it is mentioned in the steps below url (point-6) https://doc.sitecore.com/xp/en/developers/hd/211/sitecore-headless-development/create-a-sitecore-api-key.html and that is why in my other non cloud XM instance (stand alone on-prem), i am habitual to create an API and publish it, and i was doing the same in my XM Cloud Local instance too. But with local XM Cloud docker instance, It does not work that way, Because local does not work with experience edge, and when you see publishing wizard it only has one publishing target i.e "Experience edge" and that why above error com...

Hi Team, I recently have been trying to set up couple of things around XM Cloud and experience edge related things for our internal training. I was following a documentation https://doc.sitecore.com/xmc/en/developers/xm-cloud/request-a-jwt-for-experience-edge-xm-using-oauth.html to generate the experience edge token to use GraphQL for delivery API as i wanted to query results from published version of the data i.e from experience edge But the CURL command was always failing with above exception, i could figure out that there is something wrong with either the URL or connecting to it, but as everything else was working fine i thought either the format of the URL is wrong or something with it. See the documentation i refereed (it was not updated at that time, right now it is updated correctly and working fine)   I knew that there are same kind of documentation exists for XM and XM Cloud, but their URLs are different, so i tried to double check with simple XM documentation, because i ...

          Hi People, Recently, I carried out a research for our internal clients (product owners) about what it takes to go from monolith to headless and headless & composable stack (yet very far in the road map but going to XM-Cloud down the line). We are currently on Sitecore 9.1.1 (Monolith), the mainstream support for which ended in Dec 2021,  and the extended support will end in Dec 2023, so if we should continue or upgrade to 10.2 or do upgrade along with headless, all these exercise were carried out in this discovery. There were also questions like, Why one should go headless if demands are being met with current set up and version of Sitecore?  And this is the exact question which defines our (your) journey of this research and finally moving to headless, It all depends on the business needs and how far we want to go and invest. But to decide something, First we need to know what it has to offer and to understand it, this research was ca...