InfoPath Dev

I am trying to upload an InfoPath form injected with qRules to my trial of SharePoint Online, but I cannot make it work as a browser-enabled template (it works fine in InfoPath Filler). Unless I am missing something, it seems that Central Administration for SharePoint Online does not give one the option for admin approval of form templates. Is this issue related to SharePoint Online's policy of only accepting sandboxed code? If that were the case, my understanding is that would mean delving into Visual Studio, precisely what I wanted to avoid by using qRules in the first place. Is this correct or does anyone know another workaround? I am not a developer, so pardon my ignorance in advance.

Hi -- qRules forms can be deployed to sandbox -- have you tried publishing your browser form directly to a form library? I don't know anything about SharePoint Online, I'm afraid, but I have deployed qRules forms as sandboxed browser forms in our enviro.

I did try publishing the form directly to a form library. It says that "Sandboxed solutions are not enabled on the SharePoint site collection. To continue, contact a site collection or farm administrator or publish the form template as an administrator-approved form template."

So I then published the form to a SharePoint library as an administrator-approved form template. It published successfully. I can open it in InfoPath Filler but I cannot open it in the browser. I get the following error message.

This form cannot be opened in a Web browser. To open this form, use Microsoft InfoPath.
 
Click Close to exit this message.

Hide error details
Correlation ID:9c059621-8612-4da3-bba8-771a14c74d50

It seems that SharePoint Online--unlike "regular" SharePoint--does not, to my knowledge, provide a way to give admin approval to form templates, so I don't see how I can deploy a qRules form there.

At this juncture I would like to know how we can use qRules forms in an off-premises SharePoint hosting environment (whether with Microsoft or someone else) without having to package the code through Visual Studio. Any advice would be greatly appreciated.

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.

Sharepoint Online (Office 365) requires that you allocate resources for the SharePoint site collection before the sandbox is usable. 

The admin site is generally in the form https://{domain}-admin.sharepoint.com.

Assuming you are an admin, select Site Collections, check the site collection where you are trying to publish your form.  Then click the Resource Usage Quota button.  Add resources to the site and click OK. 

It may take a few minutes for the resource quota to take effect.

Just to follow up: was there any additional help we can provide for you?

Thank you for checking in. I am still unable to publish the form without errors as a template in a SharePoint library. Here is the scenario:

I have a qRules-injected browser-enabled form. Following the tutorial found on the qDabra web site, I attached a rule to a submit button that set the Command field's value to "SubmitToSharePointList /submit=ShPSubmit /mapping=mapping /id=my:id." When I run Design Checker, I get the following error: "Using custom code to save forms is not supported."

Like the early respondent suggested, I allocated plenty of resources for the site collection (10000 out of 12500 MB available) and 5000 out of 5300 resources available. I am using qRules 3.2.

I realize that this would have a simple solution in a hosting environment where I engaged the ability to give administrative approval to a form template, but SharePoint Online does not give me that. I'm not exactly sure what else I can try. In short, it is possible somehow to deploy a qRules-injected form with the "Submit to SharePoint List" functionality to a hosting environment like SharePoint Online without packaging the code through Visual Studio? I appreciate everyone's help so far.

Hi Oskar,

Can you try the following? Create a new blank form, and inject qRules. Then follow the instructions in the User Guide to publish the form to SharePoint.

The error you cite seems strange, and I'd like to see if we can repro with a vanilla qRules form.

Thanks.

Please verify you are selecting SharePoint 2010 Browser when injecting qRules and that you are not publishing as an administrator approved form.

 Hi Oskar,

Any updates on this issue? Any luck with the advice above?

Thanks.

I have not been able to devote as much time as I would like to this issue, but after following your suggestions, I am able to publish the form to SharePoint Online and open the form in a browser. The problem now is that pushing the submit button does not have any effect. I have checked and no data is being submitted to my SharePoint list.

Just to answer previous questions:

1. I used the following settings while injecting the forms. I chose "InfoPath 2010" and "Browser Compatibility."
2. The form security level is set to the default (domain).
3. The form compatability is set to a "Web Browser Form."

My qRules trial has just expired. Could that have anything to do with it? I am still able to inject the forms and to use the mapping tool.

Thank you for your help so far.

Hi - if your qRules trial has expired, the commands in the form won't run. I believe we have another trial out for download with a later expiration date if you want to download, install and re-inject.

Hilary,

Can you confirm that there are currently no limitations to using the qRules with O365?  I am currently evaluating the trial and do not want to find any suprises if I purchase.  I am using IP 2010 with O365 and need to submit repeating tables to SharePoint.

 

Thanks

Hi - if you are using the 4.0 trial, and if you are using browser forms, you may indeed run into some limitations for commands that rely on SharePoint web services. I believe you can't admin approve forms in Office 365, and have to use Sandbox only - is that correct? If so, any commands that require full trust won't be available to you.

So, if you are using Filler, your SubmitToSharePointList command should be fine. You'll need to sign into your site and click "remember me" to use the mapping form.

We are releasing 4.1 in the next week or so - it is going to have better O365 support for browser forms.

Hi Hilary, as far as I know, 'sandboxed' solutions are being deprecated in SP Online/SP2013. As are the ASMX web services and the owssvr.dll. The soap webservices and the dll will stil be around for backwords compatibility, but for how long, not sure.  This might have something to do with the problem of publishing to a sandbox, the user was experiencing.