InfoPath Dev

Hi All,

I have a submit button on my form and when I click on it to submit the form, I am getting below error:

 The form cannot be submitted because it contains validation errors. Errors are marked with either a red asterisk (required fields) or a red, dashed border (invalid values).

I verified many times and I am not able to find the error..Anyway, I want to submit the form, even though it has errors. Is there anyway to do that? I don't need any validation to submit the form.

Please advise.

Thanks

Krishna

You won't be able to submit a form with errors -- that is kind of the point of Data Validation. However, you should be able to see what fields are causing the errors -- if they don't show on your view of the form, there should be a Details button on the error message that will tell you what fields have the problem. You will want to remove the data validation (or set fields to allow blanks -- that can cause these errors as well) accordingly.

All I am able to see regarding error details is:

The form cannot be submitted because it contains validation errors. Errors are marked with either a red asterisk (required fields) or a red, dashed border (invalid values).

I do not see any field names in details..Please help.

Is this a browser form?

If it is on the client, I think usually that error message has a button on it that says Details. But, basically, if you have filled out a form and the controls that are being marked as invalid don't show in the view you are using, you are probably not going to be able to submit that filled out form. If you designed the form, you should open the form in design view and use the Logic Inspector to help you find the controls with data validation (if this is InfoPath 2007). If you did not design the form, you should contact the person who did....

On the other hand, if you see controls that have a red asterisk in them or a red border around them, try changing the value or entering a value to see if that will get your data into a valid state.

If could be a data element that is a required field ("Cannot Be Blank") but that doesn't have an associated control on the canvas.  You really just need to open the template in design mode and look for it.  I'm very surprised that the error has no extra details pointing to the data element in question.

If you attach the template (XSN), I can probably figure it out.

I just experienced this same issue...

 Turned out that I had a data field with an incorrect formula in it. I changed a "DateAndTime" field to a "Date" field but left the "now()" function in it. It needed to be changed to "today()". Many thanks to my co-developer who has received a multitude of phone calls from me...

Check those data sources! Be sure that they have the proper syntax/commands for their type!

I wish my problem was that identifiable.

I get:

The form cannot be submitted because it contains validation errors. Errors are marked with either a red asterisk (required fields) or a red, dashed border (invalid values). Field or group: my:Description Error: Cannot be blank

Click OK to resume filling out the form. You may want to check your form data for errors.

An error occurred while using the form. For more information, contact the site administrator.

An entry has been added to the Windows event log of the server.

Log ID:5567

Correlation ID:3066c9d5-e7de-43ce-a692-accc95aecdda

Hilary Stoupa:

Check that description field again - does it have any custom validation on it? Attach your template to a reply (under the Options tab) if you want me to take a quick look.

No validation whatsoever.  This error just popped up out of the blue-- I had made no changes since it last worked.  The only thing I can see is that the "people picker" is acting weird: if you make ANY changes to ANY field on the form, the picker quits working-- i.e., it will not allow you to select anyone.  No idea how or why this started happening.  Again, no changes from me, and none of my colleagues can change anything.

I deleted the Description field after I posted, and the problem persists.  This is really jacked up.  Rather than trouble you further, I'm just going to restart from scratch.  Fortunately there were only 4 projects created (PM solution).  But I'm worried this will happen again, and I have no clue what to tell my boss to put his mind at ease... really, really hate Microsoft's useless error messages.

Thanks

I'm starting to get a handle on the problem, and it took building a new list to do so.  But I still don't get what's going on.

Somehow SharePoint (or InfoPath, or both) is not letting go of old, obsolete error situations.

For instance, in the original problem, even after I deleted everything that could have caused the problem, it persisted.

So next I built a new list, and tested it column by column.  At one point I added a concatenated value to a field, but I screwed up: I added it as a default value to an existing bound text box instead of a new Calculated Value control.  The result was that the concatenated text went on forever and generated a time out when I Previewed the form.  Oops.

I realized my error and corrected it-- but from that point on, I now receive this error:

Default values, rules or code may be running in an infinite loop. To prevent this,  ensure that the default value, rule action or event handler does not update the data which causes the same rule action or event handler to execute.

So once again I stripped out any possible offenders (the original problem had already been fixed) but SharePoint refuses to acknowledge that the problem no longer really exists.

This has me completely stumped. It seems that SharePoint is "seeing" the old, error-afflicted form rather than the newly published one(s).  Do you know if it's a SharePoint or InfoPath problem?  Any idea how to correct this?

Hilary Stoupa:

Not to be silly - but did you republish the form after correcting the error?

Yep, used Quick Publish after every update.  I'm new to InfoPath with zero training-- is there a step or option I'm maybe missing?

Note: I've actually created several forms, and all were working fine until this week.  Still no clue what broke-- but this is the first time I've had forms not update after republishing, and my methods have not changed.  So I'm flabbergasted.

No, this should be fine - is this a SharePoint list form then? I might give this a try next week, see if I have something similar happen. Regular ShP 2010, not Office 365?

Hilary Stoupa:

No, this should be fine - is this a SharePoint list form then? I might give this a try next week, see if I have something similar happen. Regular ShP 2010, not Office 365?

Yes to all.  I have also contacted our site admin to see if something changed to cause this; waiting for a response.  Spent hours searching online and I swear I must be the only person this has happened to... :(

Thanks!

I have a usable solution: under SharePoint Form settings, I change to the default SharePoint form and delete the InfoPath form.  Then republish the InfoPath form: no more error message!

So apparently, as suspected, SOMEthing is not being overwritten completely, unless the InfoPath form is deleted.