# Content Picker and Dynamic Roots

**URL:** <https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655>\
**Category:** Questions\
**Tags:** v18\
**Created:** [October 14, 2026, 9:40am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655 "2026-10-14T09:40:01Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![markusjoha](https://forum.umbraco.com/user_avatar/forum.umbraco.com/markusjoha/32/141_2.png) [@markusjoha](https://forum.umbraco.com/u/markusjoha)\
**Post date:** [October 14, 2026, 9:40am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/1 "2026-10-14T09:40:01Z")

</div>

I’m working to replicate some old “Multi Node Tree Picker” behavior.

I want to create a Content Picker that renders without a tree and shows a “simple” list of options like this:

 ![image](https://forum.umbraco.com/uploads/default/original/2X/4/48c9c4076b0fdc8c6776c5e419567be0ce67a8ef.png)

However, my tree structure looks like this (I wan to show the options in the red boxes)

 ![image](https://forum.umbraco.com/uploads/default/original/2X/4/4c449f1df5cf8f761b5cdd8edf4526e36f9549eb.png)

Ideally I would like to do something like:

- Find “Hitta till oss”
- Query for descendants (at any level) of type “Office Department”

I managed to implement a custom `IDynamicRootQueryStep` that returns the Guid for all the 8 nodes that I need in the picker, but the UI renders like this:

 ![image](https://forum.umbraco.com/uploads/default/original/2X/d/d4ff0dabbce02d34aa4e5dcb198727fde5c9db3b.png)

And when I include the Offices in the query, it seems like it’s picking the first Office and render it’s children

 ![image](https://forum.umbraco.com/uploads/default/original/2X/8/89ebe4f5978a9055831f2158e44348098c52228f.png)

Is the “dynamic root” by design only able to list children of a node or I’m I missing something?

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [October 14, 2026, 9:54am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/2 "2026-10-14T09:54:44Z")

</div>

Could it be that you need to return a UDI for dyamicpath over GUID.. eg umb://document/{guid}

I think there is a utlity method in lit/c# in core to get that from a guid,

But reminded me: re flattened.. even allowed templates don’t use the flattened view they used to.. instead making the editor go searching across folders for a choice of two allowed templates. (where once two clicks selected my template, now it takes 3+ (and more if I have to expand lots of nesting to find my template)

- V17  

- V13

---

<div class="post-metadata">

**Author:** ![markusjoha](https://forum.umbraco.com/user_avatar/forum.umbraco.com/markusjoha/32/141_2.png) [@markusjoha](https://forum.umbraco.com/u/markusjoha)\
**Post date:** [October 14, 2026, 10:14am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/3 "2026-10-14T10:14:36Z")

</div>

@mistyn8,

The `IDynamicRootQueryStep`-interface wants me to return a collection of Guids.

 ![image](https://forum.umbraco.com/uploads/default/original/2X/e/efde1eeae748288f6ccfa002f2bcd667f801bda6.png)

Or in what context are you referring to?

Good find, I think that this is a problem, it would have been much better if there was a way to show a flat list of pickable items in some contexts.

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [October 14, 2026, 10:20am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/4 "2026-10-14T10:20:49Z")

</div>

Apologies, I was guessing on the dynamicpath… as Guids don’t indicate document/media/member…  
The old mntp covered all the types.. now I think the v17 approach is content picker/media picker/member picker separate pickers.

---

<div class="post-metadata">

**Author:** ![markusjoha](https://forum.umbraco.com/user_avatar/forum.umbraco.com/markusjoha/32/141_2.png) [@markusjoha](https://forum.umbraco.com/u/markusjoha)\
**Post date:** [October 14, 2026, 10:21am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/5 "2026-10-14T10:21:47Z")

</div>

Yes, the “Content Picker” can be configured to pick Documents, Media or Members which are all considered “Content” in the Umbraco-world 🙂

---

<div class="post-metadata">

**Author:** ![jonathoncove3](https://forum.umbraco.com/user_avatar/forum.umbraco.com/jonathoncove3/32/5837_2.png) [@jonathoncove3](https://forum.umbraco.com/u/jonathoncove3)\
**Post date:** [October 14, 2026, 11:18am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/6 "2026-10-14T11:18:14Z")

</div>

Could it be that providing all the parent nodes in IDynamicRootQueryStep then looks in the child folders of those nodes? So in your example you’d pass back Göteborg, Stockholm, and Jönköping?

Seems worth a try.

---

<div class="post-metadata">

**Author:** ![markusjoha](https://forum.umbraco.com/user_avatar/forum.umbraco.com/markusjoha/32/141_2.png) [@markusjoha](https://forum.umbraco.com/u/markusjoha)\
**Post date:** [October 14, 2026, 1:10pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/7 "2026-10-14T13:10:12Z")

</div>

@jonathoncove3 Yes, when I do that only the children of the first item returned is used.

From the Umbraco Core source:

```auto
if (result && result.length > 0) {
    this._rootUnique = result[0];
}

```

Seems like this on the HQ-radar

> <https://github.com/umbraco/umbraco-cms/issues/23600>
>
> \### Which Umbraco version are you using?
> 
> 17.5.3
> 
> \### Bug summary
> 
> When a Dynami…c Root query step resolves to more than one content key, the Content Picker only renders items for the first key in the roots array. The remaining resolved roots are silently dropped — they don't appear in the tree at all, collapsed or otherwise. The management API's call correctly returns all resolved keys in its roots array (confirming the server-side resolution is correct), but the subsequent tree/document/children call is only ever fired with parentId set to roots\[0\]. This makes any custom (or theoretically built-in) dynamic root step that legitimately resolves to multiple nodes of the same type effectively non-functional beyond the first result.
> 
> \### Specifics
> 
> Reproduced with a custom IDynamicRootQueryStep whose ExecuteAsync returns multiple sibling document keys (found via IDocumentNavigationQueryService.TryGetSiblingsKeysOfType).
> Confirmed via Network tab across two separate sessions (including a full application restart) that whichever key occupies position 0 in the roots array — which varies depending on content structure/sort order — is the one and only key used as parentId in the follow-up tree/document/children call. The other resolved roots are never queried.
> 
> Example captured request/response: GET /umbraco/management/api/v1/tree/document/root?...
> 
> {
> "roots": \[
> "13916098-a967-4fac-9820-027a24d224d5",
> "b09e34d2-d61b-4fd6-a30e-57355fd116c0",
> "928fb9b0-144c-4187-aca7-47201a040eb9"
> \]
> }
> 
> Followed by:
> 
> GET /umbraco/management/api/v1/tree/document/children?parentId=13916098-a967-4fac-9820-027a24d224d5&dataTypeId=...&skip=0&take=50
> 
> json
> { "total": 0, "items": \[\] }
> 
> Only 13916098-a967-4fac-9820-027a24d224d5 (roots\[0\]) is ever queried for children. The other keys never appear in any subsequent request, and never render in the tree, regardless of whether they have children of their own.
> 
> When the query step is removed entirely (origin resolves to a single node with no step), the equivalent children call works correctly and returns items — confirming the children-fetch mechanism itself is fine; it's specifically the hand-off from a multi-key roots result that's broken.
> This contradicts the documented behavior of ExecuteAsync, which states it "has to return a new collection of content keys" (plural), and the roots field itself being an array rather than a single value.
> 
> \### Steps to reproduce
> 
> Create a custom IDynamicRootQueryStep whose ExecuteAsync returns two or more content keys (e.g. resolve to several sibling nodes of the same document type via IDocumentNavigationQueryService).
> 
> Register the step via builder.DynamicRootSteps().Append\<T\>() and add a matching dynamicRootQueryStep client extension.
> 
> Configure a Content Picker Data Type with Origin = Current, append the custom step, and set "Allow items of type" to a document type that exists as a child of the resolved sibling nodes (not the siblings themselves).
> 
> Add that property to a document, ensure at least the first resolved sibling (by whatever key sorts/returns first) has no matching children, while at least one of the other resolved siblings does have matching children.
> 
> Open the Content Picker on that property.
> 
> Observe: the tree shows no items at all, despite the other resolved sibling having valid, matching children available. Confirmed via Network tab that only roots\[0\] is ever passed as parentId to tree/document/children.
> 
> \### Expected result / actual result
> 
> Expected: The Content Picker's tree should render items for all keys returned in the roots array, not just the first. If a dynamic root step resolves to multiple sibling nodes, each should appear as a browsable entry in the tree (matching the array being named roots, plural, and the documented behavior of ExecuteAsync returning "a new collection of content keys").
> 
> Actual: Only roots\[0\] is ever used to fetch and render tree items. The remaining resolved roots are dropped entirely — they don't appear in the tree collapsed, expandable, or otherwise; they're simply absent. If roots\[0\] happens to have no matching children (per the "Allow items of type" filter), the picker shows a completely empty tree even when other resolved roots have valid, selectable content underneath them. Removing the custom query step (so the origin resolves to a single node) works correctly, confirming the children-fetch mechanism itself is sound — the defect is specifically in how a multi-key roots result is handed off to it.
> 
> \---
> \_This item has been added to our backlog AB#70571\_

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [October 14, 2026, 1:15pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/8 "2026-10-14T13:15:52Z")

</div>

@markusjoha I had a bit of a look..

The backend interface (`IDynamicRootQueryStep`) uses an `ICollection<Guid>` return type because query steps can conceptually resolve multiple branch paths or unions (for example, finding matching categories or multi-site fallback roots).

And for your use case I think the dynamic root part should be returning your 3 guids..  
`Goetborg, Stockholm, Jonkoping"

However, the UI tree-picker implementation then expects a single starting node.. it can’t display multiple trees… Hence why it only shows your first tree from Offices when you include those.

(built in core are singular though.. nearest or furthest… prob due to that)

So think you are railing against a UI contraint.

You can however, create a custom property editor that also implements dynamic root setting and then either try and reuse multiple .. or just a your own ui at this point .

```json
{
  alias: "startNode",
  label: "Start node",
  description: "Limit picker to a specific node and its descendants",
  propertyEditorUiAlias: "Umb.PropertyEditorUi.ContentPicker.Source",
},

```

gets you a dynamicPath config option on the propertyEditor

---

<div class="post-metadata">

**Author:** ![Luuk](https://forum.umbraco.com/user_avatar/forum.umbraco.com/luuk/32/4446_2.png) [@Luuk](https://forum.umbraco.com/u/Luuk)\
**Post date:** [October 14, 2026, 1:19pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/9 "2026-10-14T13:19:06Z")

</div>

As far as I know, the Content Picker accepts one root path, like the ‘start node’. It’s not meant for aggregating multiple children of multiple root nodes. It’s just a filter to scope the ‘root node’. So if multiple nodes match the dynamic root, it will just take the first.

Contentment has very nice pickers where you can use queries to get what you want to do. Umbraco has a concept of [Property Editor data sources](https://docs.umbraco.com/umbraco-cms/extend-your-project/backoffice-extensions/property-editors/composition/property-editor-data-source), but that is pretty limited, so I’d go for contentment.

---

<div class="post-metadata">

**Author:** ![mistyn8](https://forum.umbraco.com/user_avatar/forum.umbraco.com/mistyn8/32/671_2.png) [@mistyn8](https://forum.umbraco.com/u/mistyn8)\
**Post date:** [October 14, 2026, 1:26pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/10 "2026-10-14T13:26:17Z")

</div>

Contentment is a great shout.. though probably would still benefit from a tree picker for the use case here.. as we have duplicated department names in the offices..  
A flat list would have to concatenate `{office}{department}` ?

Though that was actually the original request 🙂

---

<div class="post-metadata">

**Author:** ![markusjoha](https://forum.umbraco.com/user_avatar/forum.umbraco.com/markusjoha/32/141_2.png) [@markusjoha](https://forum.umbraco.com/u/markusjoha)\
**Post date:** [October 14, 2026, 1:45pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/11 "2026-10-14T13:45:07Z")

</div>

Yep, we’re using Contentment as a work around right now but would love to have a native way.

Fair, this is just a sample-app - the original use case does not have duplicates 🙂

---

<div class="post-metadata">

**Author:** ![Luuk](https://forum.umbraco.com/user_avatar/forum.umbraco.com/luuk/32/4446_2.png) [@Luuk](https://forum.umbraco.com/u/Luuk)\
**Post date:** [October 14, 2026, 2:24pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/12 "2026-10-14T14:24:49Z")

</div>

It’s fair to say that contentment is not ‘native’, but on the other hand, it exists for a long time and has a proven track record. And Lee is now even an Umbraco employee 😉 So I wouldn’t worry too much about using it; we’re using it in almost all our projects.

---

<div class="post-metadata">

**Author:** ![markusjoha](https://forum.umbraco.com/user_avatar/forum.umbraco.com/markusjoha/32/141_2.png) [@markusjoha](https://forum.umbraco.com/u/markusjoha)\
**Post date:** [October 14, 2026, 3:47pm UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/13 "2026-10-14T15:47:41Z")

</div>

I know 🙂 We use Contentment all the time 🙂 But this feels like something that could be improved in core.

---

<div class="post-metadata">

**Author:** ![Luuk](https://forum.umbraco.com/user_avatar/forum.umbraco.com/luuk/32/4446_2.png) [@Luuk](https://forum.umbraco.com/u/Luuk)\
**Post date:** [October 15, 2026, 7:13am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/14 "2026-10-15T07:13:18Z")

</div>

The closest is the is the Property Editor data sources that I mentioned before. That’s mainly used for Umbraco compose and has no real implementations yet, but it is exactly what Contentment more or less does: feed a property editor based on a data source.

---

<div class="post-metadata">

**Author:** ![PeterAtValantic](https://forum.umbraco.com/user_avatar/forum.umbraco.com/peteratvalantic/32/1343_2.png) [@PeterAtValantic](https://forum.umbraco.com/u/PeterAtValantic)\
**Post date:** [October 21, 2026, 7:27am UTC](https://forum.umbraco.com/t/content-picker-and-dynamic-roots/8655/15 "2026-10-21T07:27:05Z")

</div>

I have created a plugin for this:

> **[Add new option in Content Picker \> Query step · umbraco Umbraco-CMS ·...](https://github.com/umbraco/Umbraco-CMS/discussions/24217)**
>
> NodeNameQueryStep.zip Let say you have this tree stucture in your umbraco : Root └─ Settings └─ Feed lists ├─ Feed list (e.g. "News") ├─ Feed list (e.g. "Events") └─ Feed list (e.g. "Degrees") └─ F...
