Defining a default value for a custom property editor triggers unsaved changes on new documents

sebastiaan · March 27, 2025, 2:56pm

“default value” or as they are now called: “Property Value Preset” was released with Umbraco 15.3.0 this week:

github.com/umbraco/Umbraco-CMS

Feature: Property Value Preset

v15/dev ← v15/feature/property-value-preset

opened 03:50PM - 23 Feb 25 UTC

nielslyngsoe

+1180 -92

**Property Value Presets** A new extension point which bring the ability to pro…vide or alter the preset value for a property. Fixes https://github.com/umbraco/Umbraco-CMS/issues/17212 Contains: - Implementation for **Block Workspace**, **Content Detail Workspace**. - New Extension Point `propertyValuePreset` which takes an API, which implements the method `processValue` - `PropertyValuePresetBuilder` controller (both basic and variant version available) used to build a preset as part of the model scaffolding in a workspace. - A few updates to how Content Structure Manager and alike works. - A few updates to how Data Manager and alike works (see PR which is part of this as well: https://github.com/umbraco/Umbraco-CMS/pull/18445) - Preset for Toggle Property Editor. - Preset for slider Property Editor Preset. - Preset for MarkDown Property Editor Preset. Part of a later PR: - Make sure this works with Conditions. (Ability to know when all conditions are resolved, not necessary permitting.) - Ideally also implementation for Data-Types Workspace. Test notes: Test for invariant and variant Documents. Test for invariant and variant Blocks. Test with Blueprints?

There’s some documentation here that hopefully helps: