A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Linus Ekström
Oct 30, 2008
  2690
(0 votes)

Validation of property values

One question that I have got several times is where to do input validation for your custom property since the property architecture in EPiServer CMS 5 requires both class that handles the data and a class that is responsible for the visual presentation of the property. One way this can be done is by adding the actual validation logic before setting the input value from your PropertyControl class:

public class MyCustomProperty : PropertyString
    {
        public override IPropertyControl CreatePropertyControl()
        {
            return new MyCustomPropertyControl();
        }
    }

public class MyCustomPropertyControl : PropertyTextBoxControlBase
{
    public override void ApplyEditChanges()
    {
        string inputValue = EditControl.Text;
        if (inputValue.Length > 10)
        {
            this.AddErrorValidator("The maximum length for " + Name + " must not exceed 10 characters");
            return;
        }
        this.SetValue(inputValue);
    }
}

 

This would result in a validation message that is presented to the editor if he/she would try to enter more than 10 characters in the textbox. So, with just a few rows of code, we have added some validation for the property. But what happens if you try to set the value for the property outside the normal page edit? Or if the user changes the property with on page editing? Or if the data for the property is imported? To handle these cases we need to move the input validation to the PropertyData class:

 

public class MyCustomProperty : PropertyString
{
    public override IPropertyControl CreatePropertyControl()
    {
        return new MyCustomPropertyControl();
    }
    public override object Value
    {
        get
        {
            return base.Value;
        }
        set
        {
            ValidateInput(value as string);
            base.Value = value;
        }
    }

    private void ValidateInput(string value)
    {
        if (!String.IsNullOrEmpty(value) && value.Length > 10)
        {
            throw new Exception("The maximum length for " + Name + " must not exceed 10 characters");
        }
    }
}

public class MyCustomPropertyControl : PropertyTextBoxControlBase
    {
    }

 

This would result in the same behaviour in edit mode but now we have made sure that invalid input can not be entered from other locations as well. In this case you do not even have a need for your own property data control so you might just use one of the built in property controls instead.

 

The base class for property controls, PropertyDataControl, catches the exception and displays it to the editor in the same way as if you call the AddErrorValidator in your property control class. In other places in the ui, like the import dialog, it is also handled in the same way. If you would try to set an invalid value from your own code however, you would have to catch Exceptions and display it to the editor. You could of course also have validation both in the presentation control and in the data control if you for instance want to have a client side validation control in edit mode but still want to be sure that invalid input can not be entered from another location.

Oct 30, 2008

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026