InfoPath Dev

Hi

 

I have a form with quite a few fields that have validation rules. The form works 100% when these rules are adhered to, however if a rule is not met, the form correctly validates, a dialog box pops up and informs the user of the error with the red asterisk. Once the user has corrected the error, the form will not submit, even though there are no errors remaining. The form just does not respond to the submit button, there is no post back or anything.

It is an InfoPath 2010 form and is web browser enabled.

Any idea why this would happen? Please help.

 Thank you

 

Solly

Random idea: right click the submit button and go to browser tab and change to always post back.

 Thanks for your response, just tried it. It still doesn't work. The form does now however say it sending data to the server but once that is done it does not close (I've set a rule to close it) and the form has not been submitted.

Some error is happening on the submit.

Hi

It submits fine if all the rules are adhered to. Once it is submitted with a rule broken, then it doesn't submit thereafter.

Is there any simple way of debugging to check for the error, the submit method is a standard submit to library rule on a button.

Thank you

Hi

Is there anyway for me to find out what the error is, if any, on the submit?

I cannot find a way to debug this. The submit is using rules.

 

Thanks

Hmmm. I mean, once the validation error is fixed, it should submit... can you reproduce the issue in InfoPath Filler (i.e. in Preview)? That may make it easier to track down.

Hi

Thanks for the response. I've narrowed it down an issue when InfoPath is submitting a form using "Rules and Custom Code".

For some reason when using the standard "Submit" method for InfoPath, it will check if the form is valid first and then run the rules and then submit the form. 

However, when using "Rules and Custom Code" it will run the rules on the submit button first and then check if the form is valid and then submit or not submit. The problem for me here is, when the submit button is clicked I change the status of a variable called wf_status. My submission of a form is dependent on this variable so if my form is invalid, the variable gets changed and when the form is once valid again it won't submit because the variable doesn't meet my condition for submission.

I'm going to try and resolve this using rules otherwise I will write code for the submit method in the event.

Thanks for all the help guys :)

Hello, Did you find a workaround? I am having similar issue where form submit is based on a property value and if validation fails it won't submit even if the required fields are entered. Thanks, Andy

I am having the same issue, 4 years later. After a validation rule runs and flags a violation on my web-enabled form, nothing else--data entry nor rules--posts back. (You CAN refresh your form, but you lose all data entered thus far.) Is there some sort of handshake that's not completing? -Boonie

Looking back through this thread, the entry on 09-24-2013 10:25 PM indicates that the real culprit for the original poster is they are setting a field prior to submit that disables further submits - because if submit succeeds, they want this field set. Is your case similar? If you want to get around something like that without code, the easiest way is a double submit - have the form rules submit once, then set the helper field, then submit again.

Unfortunately, no. In my case, it's a straightforward (albeit rules-oriented) submit, i.e. just sets one field's value based on the value of another field, then submits the form. When I click the button and that control's rules are run, it identifies the validation error ("BillingEmail" is blank) and stops. (FWIW, that field is not one of those that are changed by any Submit rules.)

What I then notice after entering the required email is that the form has stopped responding entirely, even after I move the focus to another control.

I suspect that I will end up using a secondary XML data source to implement my own validation method. (sigh)

I would set up a test form - just add a required field and a submit button - see if this reproduces. Because this is not something I've seen before, so I'd wonder if it was specific to your form (or server - is your SharePoint server all up to date on its patches?).