InfoPath Dev

I recently downloaded the trial of qRules and after going through a walkthrough video, creating a mapping, and adding a control to submit rows of a repeating table to a SharePoint list I am now unable to publish my forms. When I attempt to publish it says:  "The form template has been published to the server but it can only be opened in the InfoPath filler because it contains features that are not compatible with web browsers."

When I run a design check it says that is contain "Merged print views that are not browser compatible". 

I have tried:

• Checking my views to ensure none of them are trying to print multiple views
• Remove all Views except the primary view

 I still get the error and it is prohibiting me from using the form in a browser.

Any help would be appreciated.

Would it be possible to attach the XSN form via the Options tab?

Thank you.

 It was too large.

Here is a direct link. http://dc362.4shared.com/download/Tte9qB6N/WZ_Timesheet.xsn

 I don't see anything strange with the template. I wonder if it's a publishing issue. Is sandbox enabled, or are you publishing via admin deploy?

 I tried publishing using Admin approved and get this message:

Hi-

I wonder if this happens will all forms that have custom code. The error message seems to suggest that. If that's the case, then it's SharePoint configuration and not an issue specific to the form or to qRules.

If you take a new, blank InfoPath form, add code to it, and then try to publish it to SharePoint, do you get the same error?

Thank you.

 I am still stuck on this issue. After I injected the qRules code into the form I am started seeing this problem. Currently my forms has 7 data connections.

1. mapping.xml
2. QdabraRules
3. Phase Code SP List lookup
4. Job SP List Lookup
5. Employee List Lookup
6. Submit to Web Service
7. Submit the Library

I uploaded the form as an Admin-Approved form within Central Administration and did a verify on the template. (See attached) I think the merged print view is what is blocking me but i cannot figure it out. The entire form works until I try to submit the data, using qrules, to a SP Web service. I don't even get anything in he Success, Failure, or Error message boxes from qRules. All other connections works. I have attached an image of the verify option and a copy of the xns link below.

If I run this form in Infopath and not the browser is works flawlessly.

http://dc441.4shared.com/download/vuIiCjok/WZ_Timesheet.xsn 

Do other qRules commands work in your form when you publish to the browser? Put the command node and the result node on your form and set the postback on the command node to "always". From there, when you open it in the browser after admin approving, try typing:

GenerateGuid

into the command field - you should get a result in the result field.

Can you query a SharePoint Web Service from an IP browser form in your environment without error? I have seen some environmental factors come into play in these scenarios - particularly when it works in client and fails in browser.

Another thing to try is setting the postback on your button that runs the command to "always" - but I think the issue is probably going to be with using ShP web services from a browser form.

 The error I am getting when trying to submit via the web form is "Failed to submit to SharePoint. URL = 'https://site.portal.com/sites/wzprojects/support/ehs/_vti_bin/lists.asmx'." Does it matter that it is https?

I can run GenerateGuid and it returns the Guid.

How can I test the query web service function?

If you open Internet Explorer and navigate to https://site.portal.com/sites/wzprojects/support/ehs/_vti_bin/lists.asmx, what do you get?

Re-reading Hilary's advice above (I think that's what you're asking about), and thinking about this:

"Can you query a SharePoint Web Service from an IP browser form in your environment without error? I have seen some environmental factors come into play in these scenarios - particularly when it works in client and fails in browser."

You can create a very simple form that queries, for example, the user profile service, and just make sure that if you provide a username to that web service, this executes and returns user data. This would be a simple way of verifying that you can call a SharePoint web service from a browser form.
 

 I can go to the web service page and get a list of available commands.

 I can go to the page that it reads in the error. I get a list of available operations. What can I try from here?

 I have isolated the problem to https. I have a couple of test SP farms that worked fine running HTTP. Right now my production farm runs https (Cannot change) and I have 5 forms using qrules and the SubmitToSharePointList function. They are all having the same issues. What do I need to change to allow for https?

 I have tried a couple of things. In my QA/Test farm I can setup the web service data connection to submit the the HTTP://site.portal.com/..... web service and it works fine. However, in production, IIS redirects any HTTP request to HTTPS first so I am not able to use this as a work around. In QA I installed our *.domain.com certificate under Security > Trust and that still did not allow me to submit to the web service using SSL? What do I need to do to use SSL and allow me to submit to a web service? Do I have to use the IPFS web proxy?

 I was able to find the issue. SharePoint needed the Root CA installed in the Trust to allow for the form to write to HTTPS web service. But now I am having issues with submitting. When I set the command field to GenerateGuid or SubmitToSharePointList ...... I do not get a response. I even tried setting the field to postback always.