InfoPath Dev

Able to recreate it every time... Form Publishes fine to library when qrules is not functional, but when I re-inject it with qrules, it wont work in browser.

You may want to use UDC data connections with relative URLs - then you can just upload those to a data connection library of the same name in your new enviro and approve them. Otherwise, you'll need to either walk through the data connection wizard again for each data connection, or try your hand at manually modifying the manifest after ...

If you use UDC data connections with relative URLs, you could just deploy those to your test environment - that may be simplest. Otherwise, I often save forms as source files and modify the data connections in the manifest.xsf when I'm moving things around. Of course, you need to save a backup of your template first if you decide to try ...

Well, I guess first I'd try to determine if the issue was the list of the template. I'm assuming you are adding a standard list data connection? Try with a new blank form - see if you can add a data connection to that list. At what point do you get the error in the data connection wizard?

Oh, I have seen this in the browser before. I don't know what causes it - have you had any updates to your SharePoint server recently? I do know I've seen it more often with complex XPath conditions in my formatting rule. Are you using a filter on the repeating control? Or conditional formatting? SharePoint 2010, right? If you are using ...

recreated the problem after injecting qrules. Form works in browser before injecting, but launches in infopath after being injected. Using Qrules 3.4

Some things to check:Is the form compatibilty set to Web Browser Form?When you publish, is the Enable this form to be filled out by the browser checked?After you complete publishing, does it give you a warning that the form is not browser enabled?In the SharePoint form library settings page --> Advance Settings --> Opening documents in the ...

There are several ways you can accomplish this.  Here are a couple of links that may help get you started and to help decide which method works best for your scenario: Web part mashups - http://msdn.microsoft.com/en-us/library/gg293116.aspx Master/detail control - ...

Glad to hear everything worked out great!

I personally haven't heard of any issues with Firefox using SharePoint 2010.  Maybe someone else has? I would either follow up directly with MS to see if this may be a bug, or use IE as a workaround if possible.