Qdabra qRules

Re: Need Help with QRules export to SP List

Patrick Halstead — Thu, 17 Feb 2011 07:12:54 GMT

ShP 2010 comes with "sandbox" feature which means you don't need to admin-deploy. Sorry to hear you're on MOSS 2007 still.

Hopefully, you can ask an IT operative to give you permissions. Even without qRules, you'd have to write code and get admin-deploy. qRules isn't requiring anything extra there.

Thanks for trying it out!

Re: Need Help with QRules export to SP List

illegal_operation — Wed, 16 Feb 2011 17:29:20 GMT

Well it looks like I don't have admin permissions, and they won't grant those to anyone.

So does this mean that we will be unable to use QRules in a browser based form?

Re: Need Help with QRules export to SP List

ErnestoM — Tue, 15 Feb 2011 17:21:20 GMT

Hi-

You will need to admin-deploy the form to be able to use it in the browser. The steps for this are included in the User Guide.

Please let us know if admin-deploying the form resolves the issue. Thank you.

Re: Need Help with QRules export to SP List

illegal_operation — Tue, 15 Feb 2011 17:03:30 GMT

I was able to get it to work within InfoPath, and it does exactly what we need.

But it's not working within the browser.

We are using SP2010, and I followed the instructions in the quick guide about publishing. When I get to the end, I see the error about not having 'sandbox' permissons. I asked about this, and this is currently not an option on our site.

Is there any other way to get this to work, without having the sandbox permissions?

Re: Need Help with QRules export to SP List

Hilary Stoupa — Mon, 14 Feb 2011 16:34:27 GMT

This error makes it sound as if the data connection to the Qdabra Rules XML file that is injected as a resource was converted. Open the Data Connections dialog, and select QdabraRules and click Modify. When you get to the step where the file location is indicated, click the Resource Files button and select the QdabraRules.xml resource file.

If you have trouble with these steps, attach your template to a reply (under the options tab) and I'll fix it up for you.

Also, when you injected with qRules, did you select the Browser compatibility option in the injector? Is your form saved as a browser form?

Re: Need Help with QRules export to SP List

Mel Clemente — Sun, 13 Feb 2011 14:59:35 GMT

Hi,

Are you using the SubmitToSharePointList qRules command? This document has detailed instructions on how to use it in a sample form, perhaps it might help.

Is there a data connection on your form that connects to http://team/pathtomylist/FORMS/QdabraRules.xml? qRules doesn't need to retrieve the XML from your SharePoint site, so you might want to remove that data connection, if present.

A qRules-based form template should be published as an admin-approved template. Please see the qRules User Guide > Using qRules in InfoPath Forms Services (IPFS) section for instructions on how to do that.

You should be able to test the command in Preview mode though. I'm guessing there are steps you might have missed so please try the documentation first and then let us know if you're still having trouble. You may also email us directly at Support (at) Qdabra (dot) com.

Best Regards,

Need Help with QRules export to SP List

illegal_operation — Sun, 13 Feb 2011 01:29:07 GMT

Hi,

I downloaded the trial, and trying to test out the functionality of exporting the data to a SharePoint list.

The InfoPath form we are using is a web based form.

I went through all the steps in the video, but when I preview the form. I ge the following error:

http://team/pathtomylist/FORMS/QdabraRules.xml is not valid

Is it supposed to be looking for that xml file in my document library?

So I tried to publish the form and try it from there.

When publishing, I get the following error.

"The form template has been published, but it can only be opened in InfoPath Filler because it contains features not supported with the web browsers. "

any ideas what I could have done wrong? The exporting to a SP list can be done via a web based form right? We are wanting to add this functionality to an already existing form, and it's web based.

Thanks

Chris