Meta-field controls are rendered for custom fields. You can see examples of them when you edit an entry or catalog nodes in the Catalog Management subsystem (legacy). This topic explains how to extend and customize meta-field controls.
Meta-fields are rendered using default controls that are defined in the Admin/Apps/Core/MetaData/Controls/ folder. For example, the meta-field string is rendered using ShortStringControl.ascx.
You may have more specific data entry constraints than the default controls provided. For example, you want to add a custom status text field, and you want to ensure that only specific possible values are entered in that field. You want to keep that field a simple string field (to improve performance) in the database, but also do not want users entering data to add invalid data.
The simplest way to do this is to:
Another example is when you want to override ImplementationStatus fields with a metadata field type of ShortString.
This can be done as follows:
When you edit an entry in the catalog with this meta-class (containing the ImplementationStatus field), the field is represented with your custom control.
Note: When you use custom meta-fields (such as year) with search filters in places like the Shopping Options sidebar control, use the Float type instead of Decimal.
The engine lets you override how the meta-field is rendered for the scopes listed in the following table. The position reflects the order engine validating the controls, if the control exists, which renders the field and evaluation stops.
|Specific meta field name in particular meta class||MetaClassName.MetaFieldName.TypeName.ascx|
|Specific meta field name for all meta classes||MetaFieldName.TypeName.ascx|
|Specific meta class||MetaClassName.TypeName.ascx|
Last updated: Oct 12, 2015