InfoPath Dev

Open up your SharePoint List in the browser, and then filter your list based on one of the fields you aren't sure of the name for - the URL will contain the correct field name (but may just URL encode some special chars). Another excellent tool is the U2U CAML query editor - you can find it for free here. Oh, and I adore this online URL ...

I cannot think of a code-free way you'll be able to change the name of your file and overwrite an existing file. I'd suggest you use a different naming convention and promote your CR Number to your list instead. If you want to use the built in submit functionality of InfoPath to overwrite an existing file in the library, your file name ...

Your Submit data connection uses an expression to create the file name. I'm imagining the result of this formula is different every time, which is why the file isn't overwriting. You have a second submit connection that uses just a single field for submitting -- When you resubmit a previously submitted form, what is the difference in the ...

This may depend on the SKU you are using -- I know I have a qRules form that I can use in the browser in Office 365 - What version of qRules are you running? It does need to be 3.2 for Office 365.

Create an XML file that you can use for a secondary data source for all your drop downs that need the same values. Sample attached (right click the link in the header, save locally, right click the saved file and select "Design" to open in design mode).

And the field you are setting is the same field that is used for the Submit connection in your form? Attach a copy to a reply in the options tab if you want and I can take a quick look and see if I see what may be going awry.

Is the hyperlink using data from the form? Take a look at the XML from some of your existing forms in a text editor, so you can see what the values are that are making up the hyperlink, if so. You may need to set some open rules to take care of existing.

Offhand, I'd guess your namespace definitions are different between the two forms. Compare XML from the old form and XML from the new form and take a look at the namespace stuff up at the top of the XML.

Hi: The issue is with trying to set a rule with a filter on the target field. Here's a blog post that explains how you can manually modify your manifest.xsf to specify a filtered target (like Field[Title='mytitle']). You may also want to take qRules out for a test drive - it has a command for submitting to a SharePoint list.

Good thinking on the jscript -- the initial post said VSTA was out -- but in IP 2007 you could still use jscript (in IP 2010, it is all VSTA / managed code).