InfoPath Dev

Hello,

just out of interest, not time critical and not urgent. I have a browser-enabed qRules injected form and over the course of a week I added functionality with several qRules commands, e.g. SubmitToSharePointList, submitting to multiple SP Lists after following Hilary's excellent blogs, AddAttachment, CopyTable. I'm really getting the hang of this and I absolutely love what can be done with qRules! It's exactly the right tool for someone like me: a logical mind but no skills in writing code. qRules saves my bacon and multiplies my creativity.

I also added the "Blankem" trick to clear the form, found here: http://www.infopathdev.com/forums/t/23486.aspx  -- In preview everything was hunky dory.

I published the form to the server and things turned pear shaped. Publishing to the Sandbox came back with the message that the form contains elements not compatible with the browser, so can only be used with Filler. Trying to publish as a full trust admin approved form, I got an error screen on Central Admin while uploading the form.

I took a copy of the form, removed all rules with fancy stuff and then added them one by one, publishing as a sandboxed form after each change. It turns out that the Blankem rule was the culprit. I've gone back to blanking my fields one by one and everything now works fine in the sandbox (have not tried admin approval)

Does anyone else have experience with the Blankem trick? What is the problem here? Why does it work in preview but bombs in a browser form?

Does SharePoint pick up on the manipulation of the manifest file? Or is it the xpath that does not work in a SharePoint environment?

 Ideas welcome.

cheers, Ingeborg

The issue here is that the Blankem technique involves using a Set Value destination XPath that is not a simple node path, and not something that the InfoPath designer would let you select.  While InfoPath filler will allow you to still use the form under these conditions, SharePoint will not allow it.

Luckily, you should be able to accomplish almost the same thing using a qRules command:

SetValue /xpath=//*[not(*)] | //@*[name() != 'xml:lang' and name() != 'xsi:nil'] /blank=true

Could you give that a try?

Thanks, Jimmy, that sounds like a valid explanation, although I do not have enough Xpath know how to really get the details. I'll try your suggestion after the weekend, when I'm back at my work SP environment.

cheers, Ingeborg