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