InfoPath Dev

I have a Boolean field called submitted. I have a rule that sets the field to 1 upon submit. This process works perfectly fine....except... It only works depending on where I place it in the list of rules.

Some other details: I'm sending this information to SharePoint. Using browser-based forms. Several validation fields.

So upon submit: 1. Sets Report Status
2. Creates a report number
3. Submits data
4. Sets submitted=1
5. Sends out email


If I code it this way the submitted rule doesn't get set. However, if I switch the order to:

1. Sets Report Status
2. Creates a report number
3. Sets submitted=1
4. Submits data
5. Sends out email


submitted is set to 1 BUT its set regardless if the form validates. I need the submitted field to set, iff the form is actually submitted.

We had a similar problem.

There are two ways that I can think of as a fix.  One involves disabling the submit button until all validation has been passed.  The other involes adding a second subimtted field. Both ways work.

We have one form that has alot of validation on that users can miss. Our problem was that if the form failed validation, the submitted field was still getting populated and disabling fields.

What we did to fix it was to have two fields for submitting (submitted1 and submitted2), submitted1 gets set upon submitting and submitted2 gets set after opening a form that has been submitted.

We solved it by adding a second bool field and using a rule on form open that checked to see if submitted1 was true, if yes, then set submitted2 to true.  We then used submitted2 as the field that would disable other fields.