umbraco-picker-data-source

To create a custom picker data source in Umbraco, you define an Umb extension manifest registering a propertyEditorDataSource and implement a controller class with methods like requestTreeRoot, requestItems, and search to supply structured, filtered items for backoffice property editors.

Search filtering for Umbraco tree pickers works by implementing the searchPickableFilter and search controller methods in your data source, allowing content editors to query and filter large datasets directly within the backoffice picker interface.

You need a custom collection picker data source in Umbraco when out-of-the-box property editors cannot handle tailored data shapes, specific filtering rules, or custom entity resolution by ID required for your structured datasets.

Yes, you can restrict selectable node types in Umbraco property editors by implementing a custom picker data source with query-driven search and pickable-item filtering logic to enforce which specific entities content editors are allowed to select.

To resolve selected uniques by ID in an Umbraco picker, your custom data source controller must implement the requestItems method, which fetches and returns the specific entities corresponding to the selected IDs back to the property editor.

An Umb extension manifest for property editor data sources is a configuration file in Umbraco that registers your custom picker data source with clear aliases and metadata so backoffice property editors can locate and utilize it.