Toggle in a composition preset value bug

WillemPak · September 2, 2025, 10:45am

I have a composition with a toggle. The preset value is ‘true’. When inheriting the composition the preset value is/remains false.

Using Umbraco.cms 16.1.1

Steps to reproduce:

Create a composition with a toggle preset value ‘true’

I also added a preset toggle for false for clairity.

Create page type with the same two toggles, also inherit the composition.

The same two toggles are now added twice. Directly into the page type and through the composition.

Create the node for the page type

Here you can see the toggle added directly to the page type do have their preset value. The toggles from the composition are both false.

Has anyone experienced the same? It looks to me like it is a bug.

nielslyngsoe · September 4, 2025, 12:47pm

Hi @WillemPak

That looks like a bug, and luckily one that has been fixed for 16.2 which is being released today.

github.com/umbraco/Umbraco-CMS

[V16] - Preset values/saving values doesn't work properly in compositions

opened 05:10PM - 06 Jul 25 UTC

closed 06:17AM - 13 Aug 25 UTC

MiguelGuedelha

type/bug area/frontend release/16.2.0

### Which Umbraco version are you using? 16.0.0 ### Bug summary When using a …document type that contains compositions, the fields inside said compositions if they have preset/default values, dont have said values saved into the CMS when saving/publishing the content ### Specifics _No response_ ### Steps to reproduce Fresh install of Umbraco 16 Create: 1. Toggle type with preset value as true/enabled 2. Slider type with min value 0, max value 1, step value 0.1 and starting/preset value 0.5 Create a composition with fields contain one of each data type (add them to a "Composition" tab): 1. Default toggle data type 2. Custom created toggle with default true 3. Custom created slider Now create a document type that is allowed to be created as a root node and: 1. Add the composition to it 2. Re-create the same exact fields as the composition, but on the document type itself, in a separately named tab for ease of distinction Create the document type and save it without touching any of the inputs/fields ### Expected result / actual result Expected result: 1. Both the composition and the direct fields should take their preset values Actual results: 1. Direct fields take preset values correctly 2. Composition fields don't take preset values and are then null in their respective published content access (Delivery api, etc) --- _This item has been added to our backlog AB#54968_

Let us know if you experience any problems after the upgrade