InfoPath Dev

So - it works in client (that is, in preview) but not in browser? Do you mind sharing your template? If not, could you attach it to a reply (under the Options tab) and as soon as I have a chance, I'll update it to point to one of our ShP 2010 installs, publish as a browser form and see if I have the same results.... At least then you'll ...

No, we don't map the Id field or the qRulesLastModified attribute. The commands will automatically populate those.

Hi: You need to look under tools / form options / versioning -- make sure the form is set to upgrade existing XML. If it is, there may be an issue with the latest version it is set to upgrade, but first make sure that it is set to upgrade.

Hey, congrats on getting everything working! I know that command has a lot of moving parts, but trust me when I say it gets easier. Now that you understand how it works, you'll have no problem setting it up the next time you need it. There are tons of wonderful commands you can use -- I encourage you to take a litttle time to reveiw them in ...

A screenshot of your main data source would be more helpful. But yes, I'm referring to a node in your data source (you don't have to display it on the form itself) that can be used to hold the ID from SharePoint. You only need this if you want updates in the XML to update existing form items (as opposed to creating new, which could give ...

Hi, Gabriela: You can add the same attribute to your different ID fields as a reference. Add the attribute to one field, then right click the attribute and select "Reference". You can then select another ID node you'd like to have the same attribute on. You could do the same thing for you ID fields, as well, if you wanted, so that ...

The /id parameter takes an XPath to a field in your form. Do you have a field in your form you want to use for that parameter? Do you have the Error node from the Qdabra Rules data source on your form so you can check for errors? Have you tried each submit command individually to verify each works?

No -- all SharePoint List Items have an ID -- that's built in. Don't map it. Just use the /id parameter in the command if you want your updates in your form to be reflected in your list. For your non repeating mapping submit, you'll use the full XPath to the node you want to use for the /id param (like ...

Hi -- If I understand correctly, you are submitting to 4 different lists? If so, you are going to need 4 mappings and 4 Submit data connections that use the UpdateListItems method of the lists webservice -- each Submit connection will use a different mapping for the parameters. If, instead, you are saying you want to submit some non-repeating ...