Month: March 2019

#Sitecore Experience Editor Fixing Datasource Error 404.15 (Too Many Children)

/ sitecorerunner (@reilleyweb) / Leave a comment

Recently I came across an error that I have not seen before. It seemed this error was only happening on one item. This might be something you never come across or eventually will. Either way there is a good way to prevent it.

The error I saw was below. This happened when you tried to add a datasource to a specific rendering. Not the most descriptive, but it looks like Sitecore returns a big query string of an item’s children.

After examining the rendering I noticed the query that was used in the datasouce location would actually query all children.

The easy fix was to create a components folder and keep the datasource items in there. Then the query could be changed to the following which would only look for that folder. No more errors. Of course, you can expand on the query such as adding the specific templates of the datasource.

query:./child::*[@@templateid='{02A83AA1-F53E-46E5-9BD8-A1601A1E245A}’]

#Sitecore #SCHackathon 2019 Battle of the Team X-Men Developers @ParagonDev

/ sitecorerunner (@reilleyweb) / Leave a comment

A third year in a row participating in the Sitecore Hackathon with my coworkers at Paragon. I have learned from the previous years I have done this not to make the same mistakes, mostly. See Top 5 Reasons of Failure and Top 5 Reasons the Experience Was Better. However, nothing is ever smooth in the world of web development. So here is a quick summary and lessons learned for next time.

Pre-planning:

We made sure we could get into the GitHub repos. All was good there.

Hours 1-2:

Got the hackathon rules and we started coming up with ideas. I am just going to fix my install for 9.1 that I should have done beforehand that I cannot figure out why it is not working. Well I hopefully can get that finished soon. Okay we came up with some decent ideas and time to start documenting those ideas.

Hours 3-4:

Oh look 9.1 is still not quite installed. My teammates probably want to send me over to Magneto’s team at this point. However at least our idea is solid, but wait a minute…

Hours 5-6:

We need a new idea as all our ideas were already done in different variations. Hey, look at that finally got Sitecore 9.1 working.

Hours 7-12:

Alright we have an idea that solves a problem. Let the coding begin!

Hours 13-17:

Okay finished coding. Let’s surprise our teammate with the new idea we came up with while he was taking a break. He thinks it is a good idea and documentation has begun.

Hours 18-21.5

Video created, documentation created, GitHub repo checked. Let’s finish this up and get it checked in.

Finish:

Time to sleep.

Summary and Lessons Learned

Well I haven’t learned all my lessons. I should have not assumed 9.1 would install as easy as 9.0. In my defense I did have food poisoning the day before and still feeling it. Despite that setback and getting an idea off the ground we made it in time this year. Win or lose I love doing this contest every year. It is a good time to bond with co-workers who I may not normally work and learn new things. One big thing we learned this year was keep the idea simple. That 24 hours comes quick. Solve a problem with your idea, but make sure you can do it in a good time. Documentation takes longer than you think.

Going into the Sitecore Hackathon:

Finishing: