InfoPath Dev

When I run the SubmitToSharePointList command in my infopath form, I am getting the correct item in the correct list updated as intended. I then query the list for the updated changes, blank the ID source field to be sure it doesn't use the same ID, and the form is used again. When the same command runs again it is somehow deleting the previous list item when it updates the list a 2nd time. I am not getting any type of error in the result or error fields. So I cannot currently update more than one item without closing the form and reloading it. Any ideas on why this is happening?

You aren't also using the RefreshSharePointListItems command are you?

No I'm not. I did try to use it but it really wasn't required as querying the list did the job.

And you have removed it? You may want to use the Rule Inspector and double check that.... That's the only thing I can think of that would be causing items to be deleted from your SharePoint list, as the SubmitToSharePointList command won't delete from the list.

I took a look at the rules inspector and there is nothing that is using the RefreshSharePointListItems command. I do use the SubmitToSharePointList on two different lists within the same form, but that is it. I did mess around with the Refresh command but as I said I never actually kept it in the form. Is it possible that there is some residual of that still in the form? I could recreate the form without too much trouble if I had to.

No - either the command is being used or not - if it isn't being used, I'm not sure how deletions could be occurring. Feel free to attach your form to a reply if you'd like me to take a quick look (under the options tab).

OK, here it is.

After sending I noticed that I had the qRuleslastmodified field, which is left from the Refresh command. I took that out and now it seems to be OK...

Oh, interesting! Your form doesn't have the refresh command - I saved as source files and searched, in case the rule inspector was lying to us. I'm going to check this out, see if you've found a bug here. Glad your form is working now, and thanks for letting us know!