SharePoint Form Validation supports a client-side validation for SharePoint list field data. SharePoint Form Validation provides 4 standard validation types for input content check when users create a SharePoint list item in New-Form or edit an item in Edit Form. They are Required Validation, Regular Expression Validation, Compare Validation, and Range Validation.
Administrator can configure above four validations and customize warning error messages for most columns in a list. Required Field Validator is used for setting whether some column should not be null. Regular Expression Validator is used to check whether inputted content is against a regular expression. Range Validator makes effect when it is required that some value of data should be in a range. Compare Validator plays an important role when data are set to be compared with each other.
By default, SharePoint can do some simple validations to SharePoint list field data such as "Required Field" on server side when you submit form. But users often need list field data validations of various kinds on client side. For instance, when submitter creates a task and input data in a SharePoint task list form, administrator may want him to be noticed on the client side if the data of "Start Date" column is later than "End Date" column. In such a case, SharePoint Form Validation can help administrators achieve it.
SharePoint Form Validation can be used on almost all kinds of lists. For most columns in a list, users can apply standard validation methods such as "Required Validation", "Compare Validation", "Regular Expression Validation" and "Range Validation" on columns. SharePoint Form Validation can take effect in the SharePoint list item New Form page or Edit Form page.

SharePoint Form Validation provides standard validation methods such as Require, Regular Expression, Range, Compare, when you create or edit a list item in a form. The instruction will show you how to use the SharePoint Form Validation. The following is an "Orders" list in the site.

1. Configure form validation settings
On the Settings menu
, select List Settings. Click "Form validation settings".

The Form Validation Setting page:

Click "Buyer" column. In the configuration page, select "Required Field Validator" checkbox, and type Error Message, then click "OK". It will display the error message when you input nothing on the column.

Next configure the Order No. column.
Select "Regular Expression Validator" checkbox, enter the expression ((\d){4}-(\d){4}-(\d){4}-(\d){4}) and error message. When user's input value does not match with the expression, the error message will display.

Next configure the Product column.
Select "Required Field Validator" checkbox, type the error message, and click "OK".

Next configure the Quantity column.
Select "Range Validator" checkbox, and choose "Type".
Specify the minimum value, maximum value and error message.
When entered value is not in the range, a piece of error message will remind you.

Next configure the E-mail column.
Select "Regular Expression Validator" checkbox, type the regular expression and error message, and click "OK".

Next configure the Order Data column.
Select "Required Field Validator" checkbox, type the error message, and click "OK".

Next configure the Remittance Date column.
Select "Compare Validator" checkbox.
Select Equal or Greater Than in "Operator" dropdown list, and select "Order Date" in "Column To Compare" drop-down list.
(This setting means the Remittance Date must be equal to or greater than the Order Date, or else there will be an error notification displayed in the edit form or new form.)

2. Create a new item to test the form validation setting of the list;
If the contents inputted are not in accordance with settings configured before, error messages display as bellow.

Following picture shows the result if all the validation has been passed.

Support Languages: English, Chinese, Japanese.
System Requirements
| Operating System: |
Microsoft Windows Server 2003 x86/x64 Microsoft Windows Server 2008 x86/x64 |
|---|---|
| Server: |
SharePoint Release: - Microsoft Windows SharePoint Services v3 or Microsoft Office SharePoint Server 2007 - Microsoft .NETs Framework 2.0 or 3.0 Note: This product is not compatible with SPS 2003 and WSS v2 |
| Browser: | Microsoft Internet Explorer 6 or greater is recommended for Advanced Administration features |
Release Notes
|
1.5.107.0 Jan 18th, 2010 |
Licensing module upgraded. |
|---|---|
|
1.4.820.0 Aug 21st, 2009 |
Licensing module upgraded. |
|
1.4.531.0 May 31st, 2009 |
New Feature: - Support Japanese. |
|
1.4.522.1 May 22nd, 2009 |
Licensing module upgraded. |
|
1.4.115.0 Jan 19th, 2009 |
New Feature: - List frequently-used regular expressions in setting page so that users can select one of them to use directly or edit based on them. Bug Fixed: - Fixed page error when site location was changed. |
|
1.2.1208.0 Dec 8th, 2008 |
New Features: - Availability of farm license; - Support comma formats of integer and double. Bug Fixed: - Resolved the error: validator disabled after postback. |
|
1.1.1114.1 Nov 17th, 2008 |
New Feature: - Support another five types of list: 1. Survey 2. Language and Translator 3. Slide Library 4. Wiki Page Library 5. Form Library Bugs Fixed: - Resolved the conflict with Discussion Column; - Navigation bar was missing after installation; - Inconsistent license messages. |
|
1.0.0.3834 Oct 23rd, 2008 |
Initial Release |
Thanks for your interest in this product. Choose the license you'd like below to purchase now via PayPal. If you encounter problems when trying to pay via credit card on Paypal or via bank transfer, please contact us for assistance.
Make sure to read the purchase FAQ below before you buy this product.
Site Collection License
Farm License
Purchase FAQ
An end-user is defined as any user who has access to, or has accessed any site in your Site Collection/Farm at any point in time, either directly (e.g. signing in) or indirectly (e.g. assigning him a task). Once a user has accessed a site in the site collection or the farm where the product is used, he is counted, regardless of whether or not this user is active on the specific site where the product is used. For example, while you may only have 50 users who would need to use the product on Site A in the site collection, there are 360 users accessing Site B (including the 50 accessing Site A), making a total of 360 users with access to the site collection. Since Site A and Site B are in the same site collection, you would need to purchase a license for at least 360 users. SPB licenses increase in increments of 100 users, so if there are 360 people who have access to the site collection, you will need to purchase a 400 end-user license.
If you would like to place an order with a PO, please contact sales@sharepointboost.com.

