Qdabra qRules

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Fri, 06 May 2016 22:50:34 GMT

I compared the source files - virtually the same between one of the smaller forms injected w/ qRules & one of the larger. I also created a blank test form and followed the same steps - after the initial increase in size from injecting qRules, there was a minor size bump on re-save (mainly it looks like the manifest.xsf increased in size when InfoPath changed some of the XML), but nothing like this. So I took a different qRules injected form I have for a client, which is 343 kb to being with - and followed your steps of copying and re-opening in design mode - no size change.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Thu, 05 May 2016 15:01:34 GMT

You have my email - can you send me both files? I'd like to diff them in WinMerge.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Laurie Wheeler — Thu, 05 May 2016 14:52:05 GMT

Let me know what you find out. Here are the steps I went through.

example file name file1.xsn with NOT changes being done.

right click on file1.xsn file and drag a copy into the same folder. file1.xsn and file1 - copy.xsn are same size: 261KB
Injected file1.xsn file with qRules (file1.xsn size 268KB)
Open injected file1.xsn in design mode (no changes made)
Saved file1.xsn and closed. (file1.xsn size now 411KB)
right click on file1.xsn and drag another copy into the same folder. file1.xsn is now 413KB and file1 - copy(2).xsn is 412KB

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Thu, 05 May 2016 14:36:51 GMT

qRules will initially increase the file size because of adding a code DLL and data connection. I've not seen a re-save causing the size to increase again - I'll see if I can reproduce this (it will be later this week or early next before I have a chance).

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Laurie Wheeler — Wed, 04 May 2016 19:42:27 GMT

When InfoPath designer publishes the form, there isn't any correlation ID to refer to in the logs. Our admin maxed out the limits and the form did publish 'sandboxed' on our production server (which has a test site on it). Then he changed the limits back. Our Dev server has the limits maxed out so I can keep going with development of the next pieces that will use qRules.

So.. We are at a good point!

I noticed however. The Form size has inflated.. form size was 261KB before being injected with qRules, after qRules was injected it went to 268KB. I made a copy of the form as backup and opened the original form, didn't make any changes, just performed a save to disk. The file size inflated to 411KB, and now is 412KB after another copy and open and save.

There any known issues with qRules possibly inflating the size of the file?

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Jim Cantwell — Wed, 04 May 2016 18:24:29 GMT

Did you receive a Correlation ID that you can find in the logs? I recommend using Merge-SPLogFile to find the log entries, as it will pull together the logs from all the servers.

If the error is caused by exceeding a sandbox limit, it should show in the logs. You can then adjust the specific setting that is being exceeded.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Laurie Wheeler — Wed, 04 May 2016 16:21:05 GMT

We got the form to deploy through central admin on our development server.

However, our SharePoint admin is being a little reluctant to want this form done this way, prefers it be deployed sandboxed and is hesitant to just 'max' the user code services threshold with the powershell. So, is there a way to know determine the bare minimum needed? It there some formula or rule of thumb we can use?

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Laurie Wheeler — Tue, 03 May 2016 23:56:11 GMT

When I tried it, I got a technical error from SharePoint, and I could not find the number in the logs, which I thought was odd. I have not had the chance to follow up with my SharePoint Administrator as to why this might have occurred. I hope to get with him tomorrow and have him go through the process with me. I may have missed a step. I will certainly post a reply once I find out.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Tue, 03 May 2016 22:25:27 GMT

Just wanted to follow up - were you able to try an admin deploy approach?

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Mon, 02 May 2016 17:51:57 GMT

Okay - I was able to admin deploy this form & activate to a site collection on my test server - so if this is a possibility for you, I'd certainly recommend giving it a try.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Mon, 02 May 2016 17:46:58 GMT

With a form this large and complex, I'd certainly give admin approving a try. I'm trying it now on our test server & I'll let you know the outcome.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Laurie Wheeler — Mon, 02 May 2016 17:32:08 GMT

I have the same errors with the Timeout.

So… what about promoted fields to SharePoint columns?

Right now, there are over 150 fields getting promoted to SharePoint columns (none are editable). I’m sure that as well will have an impact - removing then reduced the file size by more than 100KB.

The copy I uploaded to the forum - I removed them for testing purposes. – If I used additional data connections and qRules to have the forms data published to a SharePoint list, and called back into the form when needed.... will that eliminate promoting not so many columns?

I merged view 02 & 04 since are from the same ‘node’ within the form. Debug, and email distribution can go.. that makes (3), taking Print View out is 4. Form's file size is down from 406KB to 337KB - but still will not publish as a sandboxed browser form. I will try extending the timeout on a test server with this modified version and see what happens.

If this was a centrally deployed form.. would this issue still exist? Don't want to go that route, but might have to given the complexity and size of the form. There will be at least 3 sites using this template.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Mon, 02 May 2016 17:04:41 GMT

I'm attaching the script as a text file - it needs to be run from the server in SharePoint Management Shell - it has comments on what it is doing. I've been randomly removing views from your form to see at what point it will publish to the sandbox - I'm trying to see if there is a specific view causing the issue. So far, it seems purely size related - that is, once I remove 3 or 4 views, it will publish as browser enabled.

Obviously, you need all the views in your form - otherwise you wouldn't have created them - but if sandbox is a requirement, you may need to get the size down, even if you extend the timeout.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Hilary Stoupa — Mon, 02 May 2016 16:25:25 GMT

Oh - that explains it - I had assumed it had qRules in it. I'll re-inject and try again. I emailed you on Fiddler earlier, and I'll post the PowerShell script here after I test the form again w/ qRules.

Re: unable to open infopath 2010 in browser after injected Qrules 7.2 version

Laurie Wheeler — Mon, 02 May 2016 16:03:03 GMT

I noticed the form I sent you was not injected yet. Did you inject it with qRules and try to publish it. Once it injected it is too big to attach to the forum.

If you can send me the info to using Fiddler that will help, and for extending the timeout of SP UserCodeService. Since I sit in a different location than the actual server - there could be a issued. It takes me 3 minutes to publish the form up to SharePoint when I do it.... we have a pretty full internet pipeline.