Jeremy Davis
Jeremy Davis
Sitecore, C# and web development
Page printed from:

Posts tagged Data Templates

What happens if you duplicate field names?

We're told not to get into this state, but why?

Data Template inheritance. Most of the time it's great and a powerful tool to help you define your content schema effectively. But there are a few places where it can trip you up - and one of the interesting ones is duplicated field names. I found myself chatting about what actually happens and how this might affect PowerShell scripts and headless code recently, and it seemed worth writing down...

What happened to my Insert Options?

Proof that just because I've been doing this for a decade, I do not know it all...

I had a moment of confusion with broken Insert Options recently, which made me wonder whether I ever knew the answer behind the issue or whether I'd just forgotten it over the many years I've been working with this CMS. Either way, this needs writing down to help me remember it in the future...

Diagnosing a packaging failure

Finding the cause of very old issue...

I came across an interesting issue generating a Sitecore Package recently. Googling the issue didn't give me the whole answer, so it's time to enhance the internet again with a explanation of what I saw and why I think it happened...

Templates and help, part two

Last week I talked about an approach to displaying template-related help fields in Content Editor. The last week has been a bit manic, so I've not managed to spend much time on extending these ideas, but I have a basic approach to displaying similar data in Page Editor. Quick one today...

Help! What does this template do again?

One of the challenges of building sites with Sitecore can be making sure that your content editors understand the purpose of each template and what data they're supposed to be filling in for each field to build up their site. This can be a challenge for complex sites – the data model required for building a complex and feature packed site can sometimes be difficult to explain to non-technical editors.

Historically I've usually tackled this problem though documentation and training sessions – but it struck me the other day that Sitecore itself should be able to help too.

So I've been experimenting with the basics of a really simple prototype for explaining templates. I'll explain a what I was thinking about for Content Editor this week, and hopefully offer some ideas for adding similar behaviour to Page Editor next week.