Dynamic root cannot start at root content?

[james-whittington1]

I have a site where a settings node is outside of the site root, and there is no way to select it using the new dynamic root except picking it by key.

As an interim solution I have built a query step that gets the pages at root, but it seems like this is an origin, as it step it just discards whatever else precedes it.

An origin of "Root content" which returns the same as _contentService.GetRootContent() would be a reasonably useful kind for websites that have multiple root content nodes I think?

[bergmania]

Sounds like a okay idea, but for the specific use case, what are the problems with choosing the settings node by key? The key id not the Id, so it will be the same on all environments.

[james-whittington1]

We are using umbraco deploy so the key will (or could) change between environments as far as I am aware

[skttl]

We are using umbraco deploy so the key will (or could) change between environments as far as I am aware

Keys won't, id's will.

[james-whittington1]

Incredible. That is handy.

I do think it would be useful to have the option of selecting dynamic roots @ level 1.

For example, we have sites that are not using deploy and the key will change (if the content is manually authored in different environments).

We are using usync (for settings only) in these situations so the configuration should be the the same for each environment, so the ability to do things based on node structure rather than the key is still really important.

[simonech]

We are using umbraco deploy so the key will (or could) change between environments as far as I am aware

Keys won't, id's will.

Not everyone uses Umbraco Deploy

[simonech]

The key id not the Id, so it will be the same on all environments.

only if you sync all content via Umbraco deploy or usync publisher. Many ppl don't use either, and even if they did, normally you don't do that between multiple developers.

[james-whittington1]

Hi again, with the xpath method now being removed in 14, I think this is still relevant.

I have some sites that that I look after that are not on cloud, and just push schema changes between environments using usync. Since the content is constructed in parallel they keys are not stable.

If there was a dynamic root that could start above the content noes this would solve all the problems

-1, type:settingsNode -> use dynamic root with zero issues from here.

-1, type:homepageNode -> use dynamic root with zero issues from here too.

Dynamic root is a really good solution but I feel like I am banging my head against a wall with the way I am using it. Am I just doing it wrong, or should I expect that setting up my site with some root nodes being used to hold shared content should work gracefully.

[simonech]

I agree, I just started migrating our xpath pickers to dynamic roots, and indeed we use a lot references across roots.
Now we are building a lot of custom query step to fetch picker start nodes under other roots.
But if there was a top level root start item equivalent to _umbracoContextFactory.EnsureUmbracoContext().UmbracoContext.Content?.GetAtRoot() it would save a lot of custom code.

And the comment of umbraco deploy is not relevant for us, since we do not use it.