InfoPath Dev

So - does the form currently submit data to the second list? Submitting data to a SharePoint List from InfoPath is not very straightforward - there are ways to do it, but it isn't supported out of the box except in List forms, which only submit to a single list. Or are these form libraries? and you submit to both libraries? Sorry to be ...

Yuck. Have you tried from a different machine?

Weird. I know the form is set to close after each rule, but perhaps try checking the "don't run remaining rules" checkbox in each of your submit rules and republish. See if that helps. I realize that you have the form set to close after the actions run, and that your conditions are exclusive.... but at least it is something to try.

Any chance I can see your form? You can attach it under the options tab. If not - can you tell me what approach you took for submitting to two lists? These are lists, not libraries? You are using code, CAML, or some other approach?

Can I see a copy of your form? You can attach it under the Options tab in a reply....

Thanks so much for posting this - I'm sure it is going to help others w/ the same issue.

Try the attached - You'll see on the location field I disabled your initial rules and added one to set query fields & query, then another for the count. I changed your secondary data connection to not query on load. You'll probably want similar rules on Device, in case someone changes that after initially setting both fields. :-)

Absolutely - you can add as many fields as you need to the filter. However, how large do you expect your list to get? I'll modify a copy of your form later today to leverage query fields. Then you'll only be pulling back the data you need to count and you can get rid of your Key field.

You need to publish as a browser form & have the library set to open in the browser (under advanced settings).

Here's a sample that may help - save locally, right click & select design. You'll see in my sample, I'm not using a calculated default, but I think this approach will still work w/a calc'd default since the conditions should prevent any rule looping from resetting the field w/ the rules on it.