Property Editor Schema
Reference documentation for the propertyEditorSchema extension type
The propertyEditorSchema extension type registers a Property Editor Schema in the Umbraco backoffice. A Property Editor Schema defines the server-side data contract for a property editor, including data storage type, validation rules, and configuration options.
Manifest Structure
The manifest defines how the schema appears in the backoffice and what configuration options are available when creating Data Types.
Basic Example
A minimal schema manifest specifies which Property Editor UI should be used by default:
import type { ManifestPropertyEditorSchema } from '@umbraco-cms/backoffice/property-editor';
export const manifest: ManifestPropertyEditorSchema = {
type: 'propertyEditorSchema',
name: 'Text Box',
alias: 'Umbraco.TextBox',
meta: {
defaultPropertyEditorUiAlias: 'Umb.PropertyEditorUi.TextBox',
},
};Example with Configuration
If your Property Editor Schema has configurable settings, define them in the manifest to enable administrators to configure the Data Type in the backoffice:
Manifest Properties
The propertyEditorSchema manifest can contain the following properties:
Required Properties
type
string
Must be "propertyEditorSchema".
alias
string
Unique identifier for the schema. Must match the C# DataEditor alias.
name
string
Friendly name displayed in the backoffice.
meta
object
Metadata object containing schema configuration (see Meta Properties below).
The alias in the manifest must exactly match the alias used in the C# DataEditor attribute. The alias is the only connection between the server-side schema implementation and the client-side manifest.
Optional Properties
weight
number
Ordering weight. Higher numbers appear first in lists.
kind
string
Optional kind identifier for grouping related schemas.
Meta Properties
The meta object contains the following properties:
Required Meta Properties
defaultPropertyEditorUiAlias
string
The alias of the default Property Editor UI to use with this schema.
Optional Meta Properties
settings
object
Configuration settings for the property editor (see Settings below).
Settings Structure
The settings object defines what configuration options appear when creating or editing a Data Type:
Settings Properties Array
Each object in the properties array defines a configuration field:
alias
string
Yes
Unique identifier. Must match the C# ConfigurationEditor property name.
label
string
Yes
Display label for the configuration field.
description
string
No
Help text shown below the label.
propertyEditorUiAlias
string
Yes
The Property Editor UI to use for editing this configuration value.
config
object
No
Optional configuration to pass to the Property Editor UI.
weight
number
No
Optional ordering weight for the configuration field.
Configuration property aliases in settings.properties must match the property names defined in your C# ConfigurationEditor class. If they don't match, configuration values won't be properly passed to the backend for validation and storage.
Settings Default Data Array
Each object in the defaultData array provides default values:
alias
string
Yes
The alias of the configuration property.
value
unknown
Yes
The default value for this configuration.
Complete Example
Important Notes
Umbraco ships with default property editor schemas that you can use without creating custom C# classes.
Related Documentation
Property Editor Schema Guide - Learn about implementing the C# classes (
DataEditorandDataValueEditor).Property Editor UI Extension Type - Reference for the Property Editor UI extension type.
Creating a Property Editor Tutorial - Step-by-step guide to building a custom property editor.
Adding Server-Side Validation - Tutorial on implementing validation in your schema.
Last updated
Was this helpful?