@leekelleher what would you suggest as a best approach to making a heirarchical Contentment picker? Background: This is part of an upgrade from 7 to 10. Currently we have a heirarchy of Units, and we want reference a set of one or more units from a content node (for personalization). In 7, we import all the Units on a scheduled basis as content nodes and used a multi-node picker. But we don't actually need the Unit data as nodes in the content tree because they aren't editable by authors. We would like to import them into a standard DB table instead (much less overhead) and use (ideally) a Contentment picker. But there are thousands of nodes in a heirarchy with very similar names, so we need a heirarchical picker. Any ideas?

Hi @Deleted User, there's nothing in the Contentment's Data List editor that supports hierarchical data. I had considered the potential for developing one, but I never had an actual need for it on a project (so got put on the backburner ideas pot). What I did consider was that an MNTP-style editor would be better suited for hierarchical structures... but designing it to use Umbraco Trees, (i.e. the

ITree

and

ITreeService

interfaces), then a custom data-source could implement a custom

ITree

and the DataType configuration would select that tree-source. (Basically what MNTP could have been, not fixed to Content/Media/Member trees)