Sitecore

Hello everyone, and welcome to another blog post! In this blog, we’ll explore an important aspect of saving entities in Sitecore Content Hub, particularly during large-scale data update operations such as **backfill activities**, which are a common requirement in Content Hub implementations. Backfilling a Single Field in Sitecore Content Hub Without Fighting Required Fields If you've ever run a backfill in Sitecore Content Hub — "populate this one new property across tens of thousands of entities" — you've probably hit the wall this post is about. The task sounds trivial: load the entity, set the value, save. But the moment your entity definition has required members , and especially when some of those required members carry default values you were never told about , the "obvious" save path starts throwing errors, and you're left wondering why updating one harmless field is so hard. This is the approach that actually works: skip SaveAsync entirely ...

Hello everyone, and welcome to another blog post. Today we'll explore something interesting about the new publishing approach introduced in Sitecore AI. Specifically, we'll look at the settings worth enabling early — during template creation and development — to save yourself from unnecessary rework down the line when working with Edge Runtime publishing (V2). If you have moved to Publishing V2 in Sitecore AI (XM Cloud) and noticed that edits to a referenced or child item don't always make it to Experience Edge , you are not imagining it. Publishing V2 is built for speed, and by default it favours smaller, faster publishes over exhaustively scanning every related item (Basically in Snapshot publishing). That trade-off is great for performance, but it can leave your published content "less complete" than you expect. This post walks through the settings that control how thoroughly Publishing V2 resolves dependencies, and th...

Hello everyone! I hope you’re doing well. Let’s continue exploring how we can customize asset action visibility in a Content Hub external component. In my previous blog, Beyond Permissions: Customizing Asset Actions in Content Hub , we discussed how to hide the Download button on the asset search page for assets belonging to a specific source system. However, there’s another important aspect we haven’t covered yet: What happens when a user tries to download the same asset using a bulk operation? Hiding the Download button from the asset card is one thing, but ensuring that the same restriction applies to bulk operations is equally important. In this blog, we’ll explore how we can handle this scenario using a Content Hub external component. When policies cannot fully address this requirement, we can still rely on our trump card: an external component. In this scenario, we’ll continue using the same source system, KOL , to demonstrate how we can control asset actions for assets belo...

Hello everyone, Welcome to another blogpost. This blog will focus on Sitecore Content Hub development. We will discuss a use case that is highly relevant to practical development and reflects real-world business scenario. Let's get started without wasting any more time. Sitecore Content Hub provides a powerful security model through User Groups, Policies, Permissions, and Conditions. While these controls determine what users can do within the platform, they do not always control what users see in the user interface. Our blog will be exactly around this functionality. We received a requirement to restrict the download of certain assets from the Asset Search page. Specifically, any asset tagged with a particular taxonomy value should not be available for download by users. We explored using policies and permissions, particularly DRM rights in Content Hub, to address this requirement. However, none of the available configuration options provided a way to hide the Download button on...

Hello everyone, in this blog we will explore how the Sitecore Marketplace has transformed the Sitecore AI ecosystem. We will also look at how to get started with development and build a practical application that will be hosted on Vercel. So, let’s get started. If you’ve ever seen a content author navigate through multiple levels of the Sitecore AI content tree just to find a page they edited yesterday, you know how frustrating the experience can be. Similarly, when Sitecore developers work on stories and need to test their changes end-to-end, they often have to manually keep track of all the pages where a particular component has been added. SC Bookmarks is a Sitecore Marketplace custom app that gives Page Builder authors the ability to pin frequently edited pages, see recently visited pages, and search through their bookmarks — all from a sidebar panel that lives right next to the canvas. No more drilling through the content tree. In this post, I'll walk you through every ...