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.

Comments

Popular posts from this blog

Why SitecoreAI - Getting into the shoes of the customer how to select right CMS

Hi Team, Lately, I have been talking to lot of our customers / potential customers and having pre-sales demos where one question always comes is "Why Sitecore" ?  Now this question can be for any product which is out for sell. And as a technician I always get into product technical features, but at the same time as a pre-sales guy, it also makes me think, surely all competitive products have same features, so definitely answer to this is not in the technicalities.  If you step back and think, we are also a customer in our daily life and buy lot of things, what is that process we go through? When we buy, how can your customer decide if this is a right fit for you or not, why we select A over B? Is it price? is it service? Is it a brand? Is it about features? Is it about brand loyalty?  When it is a technical product, I am sure it cannot start with the technicalities of the product or selecting product itself, 100% not, I feel decision is always business strategy first and ...

Hell of sitecore aliases pipeline breaking the site with 500 error

Hello Friends, I belive this blog post is very important for everyone because, It has some very serious effect on working of your headless website, i will share my experience what we faced and how we resolved it Issue we started facing Our site started giving "Key cannot be null or empty" with YSOD like following  Side affect Because of this 500 error, Our site pages were showing 500 custom error page intermittently and our MAU (Monthly Active User) drop rate increased. Sitecore KB There is already Sitecore KB article talking about this error but the patch which is provided on this link is confusing as well as very huge and it could bring other issues along with it as that upgrade patch also has lot of other things too which i did not want to introduce in our stable CMS. Known Issues - Retrieving the child items of resource items is not thread-safe Observation Though the surfaced exception was looking similar and giving same error and behavior given on this article, We looked...

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