Skip to main content

Posts

The Operational Reality of Migrating Legacy Sitecore application to SitecoreAI

The Problem Enterprise tech leaders migrating from legacy Sitecore XP or non-headless SXA to SitecoreAI (the SaaS ecosystem centered around XM Cloud) often focus heavily on marketing metrics like the reported 371% ROI . However, executing a modern composable migration requires a sober look at how the underlying cost structures and technical customizations change. Moving to a locked-down SaaS platform changes your operational expense (OpEx) framework and requires you to rebuild years of monolithic code customizations. The Financial Structural Shift Migrating to SitecoreAI eliminates the traditional capital and maintenance costs of a monolithic platform, but it introduces brand-new infrastructure line items that shall not be ignored. 1. Disappearing Costs Backend Topology Maintenance: You completely eliminate the expense of hosting, scaling, and networking 10+ server roles (CM, CD, xConnect, Identity, Processing) across Azure PaaS or AWS VMs. The Upgrade Cycle: The historical burden ...
Post a Comment
Read more
Recent posts

How do Business users know if Sitecore is implemented right?

The Problem Every day, a new Sitecore project is delivered somewhere in the world. Thousands of developers, architects, consultants, and agencies help organizations implement Sitecore. But ultimately, who pays for all of it? The business. How do business stakeholders such as content authors, marketers, product owners, and technology leaders know they received value for their investment? More importantly, how do they know that a Sitecore project delivered at high speed over a few months will not become a long-term maintenance burden once the implementation partner has moved on and the support contract has ended? In theory, having a technically competent person with software architecture experience act as a gatekeeper for the client should be enough. In reality, however, Sitecore is about much more than code. It involves data modeling, information architecture, SEO, governance, content authoring experience, and platform best practices. Sitecore itself contains many concepts that have the...
Post a Comment
Read more

Sitecore JSS SDK Middleware Issue with Large Query Parameters

Recently, a fellow Sitecorian connected with me to discuss an interesting performance issue with a Sitecore JSS application running on Next.js and Vercel. The application was working perfectly fine for normal URLs. However, when users accessed the website through marketing or advertising URLs containing multiple query string parameters, the requests started taking significantly longer and eventually failed. The interesting part was that the same page worked perfectly when the query parameters were removed. Let's understand what was happening and how to fix it. The Problem The application was using Sitecore JSS with Next.js and hosted on Vercel. Normal URLs were working as expected: https://www.example.com/ Even URLs with a few query parameters were working: https://www.example.com/?p1=1&p2=2&p3=3&p4=4&p5=5 But when the number of query parameters increased, the request started taking much longer and eventually failed. In some cases, we were seeing errors such as: 504...
Post a Comment
Read more

Understanding timezones in Sitecore Pages and how to update Sitecore Pages timezone

One of our content authors recently raised a simple question: "Why does the Publish Date in Sitecore Pages show UTC instead of my local time?" Here is what it looks like in SitecoreAI -  It pretty much clarifies that this is an expected behavior and the timezone being shown to user is UTC. But it does not tell what can we do to make it follow local time zone. Understanding the behavior Sitecore stores Date and Datetime values in UTC , ensuring consistency across environments and deployments. When these values are displayed in Sitecore Pages, they are rendered using the server's configured timezone , not the individual author's browser or local timezone . This means: ✔️ Data is stored consistently in UTC. ✔️ Display is based on the server timezone. ❌ There is currently no documented configuration to display dates in each author's local timezone. If your server timezone needs to be adjusted globally, Sitecore provides the following configuration: <setting name=...
Post a Comment
Read more

Mastering Field-Level Security in Sitecore XM Cloud: Why Your 'Field Write' Option is Missing

As Sitecore architects, we often face a specific requirement: Read-Only Fields. Whether you are pulling product data from a PIM, customer IDs from a CRM, or metadata from an external ERP, you need those fields to be visible to Content Authors but strictly uneditable. The goal is simple: the external system is the "Source of Truth," and manual edits in Sitecore would cause data desync. Recently, a common hurdle has surfaced in XM Cloud environments regarding Field Write permissions. Let’s dive into why this happens and how to fix it. The Challenge Typically, to make a field read-only across an entire site, we: Open the Security Editor . Enable the Field Write column. Deny Field Write on the Template item, expecting it to propagate to all content items. The Problem: Many developers report that while they can see the "Field Write" column, the option to actually assign a "Deny" or "Grant" is missing when selecting the Template item itself. Why i...
Post a Comment
Read more