Skip to main content

XM Cloud - Place holders path missing from serialization module

Hi Team,

As i have been setting up Sitecore XM Cloud instance, I have been following the guide Set up local , Which is the best guide available to get started with XM Cloud, i have been following the same but there are some issues with that page which i already have raised previously and have also get them verified with Sitecore support too.

Similar thing i found before few days, After all serialization module given on the https://doc.sitecore.com/xmc/en/developers/xm-cloud/walkthrough--setting-up-your-full-stack-xm-cloud-local-development-environment.html  link, There are some steps given on to create serialization module and it also ships with one .module.json file too

But when you use that guidelines and serialize things in your local by fetching from cloud instance and pushing it into your local instance, One of the item shows GUID instead of item


Solution

If you closely see the module.json given on the guide, it is only showing couple of item paths to be serialized 


As you can see it only suggest to have these three items to be added to module.json file, now when you actually do pull from cloud and push into your local, it uses same module files and syncs items into local (Though it is just a get started guide, and will not have all the detailed serialization, But because if we follow this guide we will end up having GUID instead of item path and hence it think what ever items are needed should be part of this starter guide and hence it needs to be fixed)

But because the site's setting item expects the reference to "Placeholders Path" item too, and Because the Sitecore->Layout->Place holder Settings path is not present in the serialization module, it is not creating that item, but setting item is already expecting that item, and because it is not able to find that physical place holder settings item path, it is showing the GUID

FIX

Because serialization is expecting this item, Just add below in the serialization module 

{
          "name": "layout",
          "path": "/sitecore/layout/Placeholder Settings/Project/<sitename>",
         "allowedPushOperations": "CreateAndUpdate"
} 

Now if you delete all serialized item folders from the disk and re-run the steps by fetching from XM Cloud remote instance and push it into local instance, you will see that now the items is just showing fine, Because it has been included in the serialization module which setting's item was expecting


I have raised this with Sitecore support team about this behavior and they have acknowledged the behavior and they have registered this as a bug, It should be rolled out soon.

Thank you.

Labels:

Comments

Post a Comment

Popular posts from this blog

401.1 Unauthorized with windows authentication error code 0xc000006d

How many of you have faced this hosting issue when you do everything what it takes to run the site with windows authentication but still you are getting the same error again and again? If you think you also have faced the same issue and you tired of reading MSDN KBs for it and still have not found the issue (If KB has solved the issue, well and good, if not you can try this trick),Please Read below Typical scenario In typical hosting with IIS, i did every possible things like enabling windows authentication, changing it in web.config, configuring connection pool, authorization rules, it asks me for window authentication login and despite of entering correct credentials it always fails and keeps on asking for login, and when pressed cancel it gives 401.1 with 0xc000006d error code Solution (Which worked for me at-least after trying for almost 6-9 hrs) You need to change the Loop Back Check in registry so that it allows the host names which you are giving in url are allowed and au...
2 comments
Read more

Set up leprechaun code generation with Sitecore XM Cloud Starterkit

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 othe...
Post a Comment
Read more

Zero to Hero - A real life RCA of exact issue in Sitecore Managed Cloud environment

Hello All, The purpose of today's post is to share a real life burning and escalated scenario which was new to me and how did I approach it and how big the escalations were and what was the outcome Sitecore's goodwill was at stack not because Sitecore is not capable of handling it but just because our environment was Sitecore Managed Cloud, and any issue that comes if its infra, back end code, front end code will be first pointed as Sitecore issue and that is where our consultancy and experience will play a role to prove that it is not Sitecore issue.  Issue we faced Out of the blue our site started giving "504 Gateway Time-out", and it was reported that almost everyone is getting this error, but when we used to browse the site, everything looked good and never 504. 504 Gateway Time-out error tells that, That the request went to Content Delivery servers of Sitecore from gateway, but gateway did not get response in time from those CDs and hence it gave time out error. ...
2 comments
Read more