Validation Overview

• Aug 01, 2019
• 2 minutes to read

The ASPxEditors Suite provides the powerful built-in flexibility to perform data validation both on the client and server. It allows you to easily implement different validation scenarios without using additional validator controls.

Editor validation can be forced in different ways (see the image below).

Validation on Leave. When the ValidationSettings.ValidateOnLeave property is set to true (the default value), editor value changes causes validation.

Validation Methods. Validation can be forced by calling the following methods.

• On the client side - ASPxClientEdit.Validate, ASPxClientEdit.ValidateEditorsInContainer, ASPxClientEdit.ValidateEditorsInContainerById, and ASPxClientEdit.ValidateGroup.
• On the server side - ASPxEdit.Validate and ASPxEdit.ValidateEditorsInContainer.

Other Editors. Certain editors can force editor validation if their CausesValidation property is set to true.

• If ASPxButton's ASPxButton.CausesValidation property is set to true (the default value), then the button click forces editor validation. The button's properties can be used to specify a group of editors to validate (ASPxButton.ValidationGroup), a container for whose controls the button causes validation (ASPxButton.ValidationContainerID), and whether invisible editors should be validated together with visible ones (ASPxButton.ValidateInvisibleEditors).
• If an editor's ValidationSettings.CausesValidation and ASPxEdit.AutoPostBack properties are set to true, the validation of the editor forces a whole group (specified via the ValidationSettings.ValidationGroup property) validation.

Concepts

• Validation Settings
• Validation Error Message
• Validation Summary
• Examples