4

Summary

I have a single control with two (almost) identical validators, each linked to two validation groups. When the cursor leaves the control, both validators are automatically checked by ASP.NET. Is there a way to only fire one (without setting EnableClientScript="false") so there are not two * symbols being displayed on the blur?

Details

I have a form with two buttons asp:btnSave and asp:btnSubmit... both buttons require validation, as certain controls must be validated on the save for it to work correctly.

So I have two validation groups, the "default" group for submitting (i.e. ValidationGroup property is NOT set), and the "SaveGroup" for saving. There are two asp:ValidationSummary controls to reflect these.

On a single control that is (for example) designed to accept a decimal value, I have the following. Firstly a required field for the submit, then a range validator for the submit. Then a 3rd validator which is a replication of the range validator but is part of the "SaveGroup"...

<asp:TextBox runat="server" id="txtMyDecVal" />
<asp:RequiredFieldValidator runat="server" ControlToValidate="txtMyDecVal" 
   Text="*" ErrorMessage="Enter a value" />
<asp:RangeValidator runat="server" ControlToValidate="txtMyDecVal" Type="Double"
   MinimumValue="0" MaximumValue="999.99" Text="*"
   ErrorMessage="Value must be between 0 and 999.99" />
<asp:RangeValidator runat="server" ControlToValidate="txtMyDecVal" Type="Double"
   MinimumValue="0" MaximumValue="999.99" Text="*"
   ErrorMessage="Value must be between 0 and 999.99"
   ValidationGroup="SaveGroup" />

This is working fine, and the two buttons validate correctly.

The problem is... there is a visual issue that if you type invalid text into the control, BOTH the RangeValidators are fired automatically by ASP.NET when the cursor leaves the control, resulting in two * symbols appearing.

Is there a way to make it so that only one of those validators are checked as part of the blur event on the control?

I could set EnableClientScript="false" on one of the validators, but I still want it to check the control on the client side without a post-back first.

Update

I have been playing with setting EnableClientScript="false" as I decided that the post-back on the save wasn't actually going to be a big issue.

However, this then leads on to another visual issue: Enter invalid text, the "submit" validator shows the *. Click the save, which posts-back and then displays the * for the "save" validator. If you then change the text to valid text, the "save" validator doesn't disappear, so it still looks like there's a problem... and if you change the text to different invalid text, you get the "submit" * appearing as well, resulting in the same as before... i.e. two * symbols.

freefaller
  • 19,368
  • 7
  • 57
  • 87
  • Get anywhere with this? There's some interesting details here: http://www.codedigest.com/Articles/ASPNET/166_Restrict_AspNet_Validator_controls_to_Fire_on_Page_Submit.aspx -- where validators are disabled on page load and then enabled (potentially with a particular validation group) on a (submit) control click. – Mayyit Aug 03 '14 at 12:46

3 Answers3

1

You should add Display="Dynamic" to your validators.

<asp:RequiredFieldValidator runat="server" ControlToValidate="txtMyDecVal" 
   Text="*" ErrorMessage="Enter a value" Display="Dynamic" />
<asp:RangeValidator runat="server" ControlToValidate="txtMyDecVal" Type="Double"
   MinimumValue="0" MaximumValue="999.99" Text="*"
   ErrorMessage="Value must be between 0 and 999.99" Display="Dynamic" />
<asp:RangeValidator runat="server" ControlToValidate="txtMyDecVal" Type="Double"
   MinimumValue="0" MaximumValue="999.99" Text="*"
   ErrorMessage="Value must be between 0 and 999.99"
   ValidationGroup="SaveGroup"  Display="Dynamic"/>
Irfan TahirKheli
  • 3,652
  • 1
  • 22
  • 36
  • Thanks @Irfan, but how will that stop one of the validators being fired on the `blur` event? All `Display="Dynamic"` will do is remove the space being used by the `*` symbol unless it needs to be displayed – freefaller Dec 02 '13 at 14:06
  • ah you mean two different groups of validation. I thought its the same group. – Irfan TahirKheli Dec 02 '13 at 14:10
  • 1
    That would explain the confusion... although I think I mention there are multiple validation groups about 4 times in the question – freefaller Dec 02 '13 at 14:16
0

Courtesy of Satheesh babu's artice, and having toyed with a couple of options -- I think the best way to deal with complex situations is to DIY.

I've set CausesValidation="False" and removed ValidationGroups from buttons, and put something like:

    OnClientClick="if (EnableVal(['ValidationGroup1','ValidationGroup2']) == false) {return false;}"

for client-side validations, where particular buttons validate increasingly complex rules as the process moves ahead. This allows me to reduce duplicating validators.

Then, on server-side, I am calling Page.Validate("ValidationGroup#") for each group, depending on the buttons or even business process state, and then finally checking Page.IsValid.

Also, depending on the business process state, the buttons' OnClientClicks can be set from code-behind depending on which validation groups I want to deal with right now.

Finally, to combine validation summaries, see the javascript here: Page_ClientValidate() with multiple ValidationGroups - how to show multiple summaries simultaneously? (with some tweaks).

Net very elegant, but probably gives the most control.

Community
  • 1
  • 1
Mayyit
  • 413
  • 5
  • 10
  • Hi @Mayyit - thanks for the answer. To be honest, I can't remember how I solved it (if I solved it at all). Will check if I have time tomorrow, when I'm back in front of the development machine – freefaller Aug 03 '14 at 16:56
0

I am faced with this issue too - I have:

  • Multiple ValidationGroups triggered by different buttons
  • Validations that need to take place in both groups (in my case RequiredFieldValidators)

Adding multiple validators works as above until you enter and then subsequently blank out a field - you get both messages. My workaround is as follows:

Overwrite the IsValidationGroupMatch JavaScript method to allow for comma seperated values in the ValidationGroup property:

function IsValidationGroupMatch(control, validationGroup) {
    if ((typeof (validationGroup) == "undefined") || (validationGroup == null)) {
        return true;
    }
    var controlGroup = "";
    if (typeof (control.validationGroup) == "string") {
        controlGroup = control.validationGroup;
    }

    //return (controlGroup == validationGroup);

    var controlValidationGroups = controlGroup.split(",");
    return (controlValidationGroups.indexOf(validationGroup) > -1);
}

Then in the ASP you add:

<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"
    ControlToValidate="TextBox1" ValidationGroup="VG1,VG2" Display="Dynamic">
    Text box is required
</asp:RequiredFieldValidator>
<asp:Button ID="Button1" runat="server" Text="Validate VG1"
    OnClick="Button1_Click" ValidationGroup="VG1" />
<asp:Button ID="Button2" runat="server" Text="Validate VG2"
    OnClick="Button2_Click" ValidationGroup="VG2" />

This works on the client, but on the server you would need to add custom line(s) of code to ensure the controls listed as needing to be validated by both are checked:

// controls listed as part of ValidationGroup 'VG1' will have had their
// validation tested, ones listed as 'VG1,VG2', 'VG2,VG1' etc would not
protected void Button1_Click(object sender, EventArgs e)
{
    Page.Validate("VG1,VG2");
    if (!Page.IsValid)
        return;

    // do something
}

This way the validation controls are only needed to be added once but can be implemented for multiple ValidationGroups. It's really only a workaround/hack that works on the client, the extra checks on the all-important server side validation will need to be done manually each time.

DenverCoder9
  • 1,119
  • 3
  • 16
  • 30