In Umbraco 13 we create a custom property editor, which re-used configuration from MNTP, but a different property editor to implement a different reference via GetReferences() instead of default reference. In Umbraco 17 it looks something like this: [DataEditor( //name: "Alternative Page Relat…

Ah so realistically you want to use the UI of the MNTP but have a custom DataEditor to handle the data differently? I think you approach in itself is sound. You don’t need to copy the editor ui file though. The UmbPropertyEditorUIContentPickerElement class is not part of the public package exports …

I think the approach is my answer in that thread you mentioned: [image] Can I include a built in property for my custom property group? speech_balloonQuestions I’m not sure if this is the best approach, but maybe this could be helpful:

I had a look at umb-property-dataset previously, but IIRC it required the umb-property and render label/description here, which isn’t what a want inside a custom property editor.

So let me see if I get this right: you want to create a custom property editor that reuses the editor UI for the MNTP, but has custom handling of the data?

It is mainly the same feature as MTNP, just to set a different relation type in tracked reference instead if the default as I can use IRelationService to get these specific references for a content node (and not any other pickers where this node is picked). However I want to remain the standard MNT…

Ah wait, the Property Value Converter is not sealed, so I think you can actually do something like this: public class AlternativePageRelationPickerValueConverter : MultiNodeTreePickerValueConverter { public override bool IsConverter(IPublishedPropertyType propertyType) => propertyType.E…

Yes, it was quite simple in old back office using view, but e.g. different converter or omit some configuration properties - eventually setting defaults. I will have a look at this.

Not sure it it would work as I think is ConvertSourceToIntermediate() and ConvertIntermediateToObject() only handle this editor aliases. src/Umbraco.Core/PropertyEditors/ValueConverters/MultiNodeTreePickerValueConverter.cs main } // TODO: In…

Oh that is really lame…. that’s what the public override bool IsConverter(IPublishedPropertyType propertyType) => propertyType.EditorAlias.Equals(Constants.PropertyEditors.Aliases.MultiNodeTreePicker); is for!

This seems to work well and simplifies it a bit. Just using UmbInputDocumentElement and UmbChangeEvent instead. import { customElement, html, property } from '@umbraco-cms/backoffice/external/lit'; import { UmbInputDocumentElement } from "@umbraco-cms/backoffice/document"; import { UmbLitElement …

Reuse property editor UI for custom property editor

Questions

Luuk (Luuk Peters (Proud Nerds)) April 28, 2026, 7:34am 2

I think the approach is my answer in that thread you mentioned: