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...
When configuring a Sitecore production environment on VMs (on-prem or cloud) , it’s critical to define and open only the necessary network ports between the servers to ensure secure and functional communication between the roles (CM, CD, Solr, SQL, Redis, Identity, etc.). Below is a breakdown of recommended ports that should be opened between VMs in a scaled Sitecore XP 10.x environment : 🔐 Core Port Recommendations Source VM Target VM Port(s) Protocol Purpose ...