InfoPath Dev

Oh, I'm glad you have a work around! I still want to try this sometime this week, see if I can repro on one of our servers... :-)

Okay - just tried this - and my form updated correctly. That is, I modified my IP SharePoint List form to make a field required and published. I verified when I opened an item, the field is now required. I modified the form to make the field not required - republished, and the field is no longer required. You may want to let your SharePoint admin know about this (if you are the admin, check your logs and see if you can figure out what's going on ....)

 if you have a control, and you applied rules against that control, and then later you delete that control, the rules will still be active against that control.

One way to check if the above is causing the validation error is go to Data->Rule Inspector and check if there are rules still been applied to control that are no longer in your form.

Same issue here. We running InfoPath 2007. Developer has left and I am a bit stuck. I check the rules behind the Submit button and spot something of concern. There are 5 stage fields (stage1, stage2 .... stage5) being set but the value looks corrupted. Set a fields values: stage1 = "ðððþððð" 2 questions: 1. Could this cause the form to error thinking that a field needs to be set? 2. How do I find the meaning of these values?

I had the same thing happen to me today.  I had marked 2 fields as required in my form, but then changed them when I realized I didn't want them required.  However, InfoPath kept insisting that I had fields that were not completed that were marked required.  There was no red fuzzies, or dotted lines.  just the error.  So I tried the above.. I exported the files locally, then deleted the template.xsn from the forms folder, then republished from my local copy.  And there you have it: a working form.  Not that I spent the last 4 hours trying to figure it out!  Oh well.. Thanks for this post!  Without it, I would be another 4 hours in before I finally give up and start over!

Hello, I have an InfoPath form with 2 Date and Time columns, named Created and Target Implement Date. The request is to make the form accept a submission with a Target Implement Date greater than or equal to today. Currently only future dates are allowed. Creating a Validation Rule Condition of Target Implement Date is less than now(), but this does not allow us to choose today. This works for limiting to future dates, but if we pick today's date, the form fails to submit with the following error: "One or more fields have invalid values and cannot be submitted to the list."