Qdabra qRules

Re: Cannot publish because of merged print view

kameronberget — Tue, 20 Dec 2011 05:25:24 GMT

This is fixed. The problem was due to SLL being used. To fix I created an identity in the secure store service and configured my UDCX file to sue the secure store ID.

Re: Cannot publish because of merged print view

Hilary Stoupa — Wed, 07 Dec 2011 20:52:01 GMT

I understand not wanting to have the field on the form, the purpose is to be able to set it via rules, etc.

I do not know of a reason that the command would work sometimes, which is what I think you are saying is currently happening. I do notice on your form the Submit button does not have postback set to "always" - it would be helpful to add that.

Could you temporarily add the Error node from the Qdabra Rules data source, and temporarily change your submit button to not close on submit, so that you could try again in the browser and see if qRules is returning any error in the instances where it fails?

Re: Cannot publish because of merged print view

kameronberget — Wed, 07 Dec 2011 15:26:16 GMT

I don't actually want to have the field in the form. I did 20-30 tests last night and it worked about two times. This is in production now and I can't have this happening. I have attached a link since my form is over the limit......

http://www.4shared.com/file/svnzeczs/WZ-JobsiteSafetyCheck_New.html

Re: Cannot publish because of merged print view

Hilary Stoupa — Wed, 07 Dec 2011 01:52:51 GMT

You have the postback on the command node set to always? And it works when you paste the command in from preview but not when you enter the same command in the browser?

I'd like to see your form template - can you either attach it to the Options tab or send it to Support AT Qdabra DOT com and mention this thread in the email?

Thanks!

Re: Cannot publish because of merged print view

kameronberget — Tue, 06 Dec 2011 21:03:58 GMT

If I open the form is preview and paste the SubmitToSharePointList command or GenerateGuid command it works. If I do that same thing in the browser nothing happens. I tested these yesterday in thee browser and they all worked fine. Any idea why the command field would just stop working? Right now I am using a Submit button to set the command field value to SubmitToSharePointList /submit=SharePointListSubmit /mapping=mapping /id=my:ID

Re: Cannot publish because of merged print view

kameronberget — Tue, 06 Dec 2011 20:45:47 GMT

I tried that and my form works in the client but in the browser it does nothing.

Re: Cannot publish because of merged print view

Hilary Stoupa — Mon, 05 Dec 2011 23:21:19 GMT

If GenerateGuid is failing, you may have accidentally disabled qRules in your form. Try re-injecting.

Re: Cannot publish because of merged print view

kameronberget — Mon, 05 Dec 2011 18:38:47 GMT

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.

Re: Cannot publish because of merged print view

kameronberget — Sat, 26 Nov 2011 20:10:07 GMT

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?

Re: Cannot publish because of merged print view

kameronberget — Fri, 25 Nov 2011 14:52:18 GMT

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?

Re: Cannot publish because of merged print view

kameronberget — Fri, 25 Nov 2011 14:21:35 GMT

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?

Re: Cannot publish because of merged print view

kameronberget — Thu, 24 Nov 2011 17:44:31 GMT

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

Re: Cannot publish because of merged print view

ErnestoM — Thu, 24 Nov 2011 17:43:22 GMT

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.

Re: Cannot publish because of merged print view

kameronberget — Thu, 24 Nov 2011 17:27:49 GMT

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?

Re: Cannot publish because of merged print view

Hilary Stoupa — Thu, 27 Oct 2011 22:24:26 GMT

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.