> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/extend-your-project/tutorials/creating-a-property-editor/adding-server-side-validation/default-property-editor-schema-aliases.md).

# Default Property Editor Schema Aliases

In the following section, you will find a list of the default Property Editor Schema aliases in Umbraco. We recommend you use one of these as `propertyEditorSchemaAlias` when defining a custom Property Editor in `umbraco-package.json`.

The chosen Property Editor Schema determines the resulting .NET runtime type of the stored Property Editor data. As this will ultimately be used when rendering the website, it is important to choose an appropriate Property Editor Schema.

| Property Editor Schema alias | .NET runtime type               |
| ---------------------------- | ------------------------------- |
| Umbraco.Plain.DateTime       | `System.DateTime`               |
| Umbraco.Plain.Decimal        | `System.Decimal`                |
| Umbraco.Plain.Integer        | `System.Int32`                  |
| Umbraco.Plain.Json           | `System.Text.Json.JsonDocument` |
| Umbraco.Plain.String         | `System.String`                 |
| Umbraco.Plain.Time           | `System.TimeSpan`               |

{% hint style="info" %}
You can perform custom conversion of the stored Property Editor data by implementing your own [Property Value Converter](/umbraco-cms/extend-your-project/tutorials/creating-a-property-editor/custom-value-conversion-for-rendering.md). In this case, the chosen Property Editor Schema determines the input data for the custom conversion.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.umbraco.com/umbraco-cms/extend-your-project/tutorials/creating-a-property-editor/adding-server-side-validation/default-property-editor-schema-aliases.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.