General

Re: Empty emails

Jay@Work — Sun, 17 Jun 2012 20:23:01 GMT

Were it a browser enabled form I could have used a hyperlink and opened a new browser in a new window.
Looking back on this and another thread, it seems the reason I switch to a form filler was to be able to print merged views.

Re: Empty emails

Hilary Stoupa — Thu, 14 Jun 2012 16:29:45 GMT

My guess is that the code you are using to launch the browser may not be allowed in a browser form.

Re: Empty emails

Jay@Work — Thu, 14 Jun 2012 01:36:35 GMT

Sorry my mistake, it's a form filler I was deploying.
It used to be a browser form until the user requirements took it beyond that.... it was only after I converted it to filler that I put code behind in it.

I just created a simple test browser form. 2 buttons, 1 to email submit and 1 to launch a browser (using code) and when I try and publish I get messages about requiring approval.
The user requirements for this have changed so often now I can't even remember why I went down the filler road now!

Re: Empty emails

Hilary Stoupa — Thu, 14 Jun 2012 00:59:22 GMT

You are able to publish to a library as a Browser form? And your email submit works? This link says:

Note that there are certain restrictions to deploying your form as a sandboxed solution:

Must be an InfoPath 2010 form.
Must use C# or Visual Basic as the programming language.
Cannot submit to e-mail data connections.
Cannot have properties promoted for part-to-part connections.
Must not have any managed meta-data controls or data connections.

Re: Empty emails

Jay@Work — Thu, 14 Jun 2012 00:50:03 GMT

My form filler has all of the above... code behind (to launch a browser window when an image button is pressed) and an email submit connection but I don't get any prompts when I simply publish the form to the forms library. Nor when I run it.
I'll check the link

Re: Empty emails

Hilary Stoupa — Thu, 14 Jun 2012 00:25:15 GMT

I don't mean to confuse you. If your forms do not have code, as I've mentioned, this is simply not an issue for you and you can keep publishing to a form library. If your forms did have code, and an email submit connection, you'd have to admin approve the form (as outlined in the link I provided above) to open them in the browser.

Admin approving a form template means it has been published in a specific fashion to a network location, uploaded to Central Admin and activated, then used as a content type in a form library.

Re: Empty emails

Jay@Work — Thu, 14 Jun 2012 00:15:11 GMT

I publish both types in the same way... to a forms library.
I'm the farm admin if that's what you mean though?

Re: Empty emails

Hilary Stoupa — Thu, 14 Jun 2012 00:04:28 GMT

I'm guessing you currently just publish your browser form to a form library?

If you were to add code to your form, and had an email submit data connection, it would have to be uploaded via Central Admin - more here.

But yes, I would anticipate the only thing that will resolve the blank emails from Filler would be to use the same versions of Office for both InfoPath and Outlook.

Re: Empty emails

Jay@Work — Wed, 13 Jun 2012 23:56:37 GMT

So unless we can upgrade these particular users to Outlook 2010 we are stuck with browser enabled for this?

How do you mean "admin approved"?

Re: Empty emails

Hilary Stoupa — Wed, 13 Jun 2012 23:08:41 GMT

It is the different versions of Office - we have seen blank emails with Outlook 2007 and IP 2010. As to the browser - I like that so much better, don't you? No pop-up and the user can't cancel the email. So you know, if you add any code to your form, it will have to be admin approved to use an email submit connection (that bit of info surprised me when I learned it, so I thought I'd mention it now...)

Re: Empty emails

Jay@Work — Wed, 13 Jun 2012 22:19:56 GMT

Converted the form filler to a browser based form and all is well, I get an email with the form in the body of the email.
One other thing I notice is that when browser based I don't see the email it just arrives, when using a form filler an outlook generated email pops up and requires clicking send.

My *guess* is that forms services is genrating an email and doing it as it should whereas a form filler email is generated with/in outlook and outlook 2003 isn't behaving

Re: Empty emails

Jay@Work — Wed, 13 Jun 2012 22:14:54 GMT

IP 2010 and Outlook (blush) 2003. A couple of apps are preventing us from going to Outlook 2010 but we are addressing this.

The inline view worked perfectly when this form was a browser enabled one. I'll do a test by creating a browser form and see if that works. That way I'll know if we are dealing with a filler thing or something has recently broken.

Re: Empty emails

Hilary Stoupa — Wed, 13 Jun 2012 21:52:37 GMT

Okay - same versions of IP and Outlook? Both are 2010? or 2007?

Re: Empty emails

Jay@Work — Wed, 13 Jun 2012 21:46:47 GMT

Yikes... Just created a brand new form filler. Popped a button on the form and set up a data connection to email (me) the view inline (no attachment).
When I click the button the same thing happens, the body of the email only contains the intro. No view. This happens in both published and preview mode

Re: Empty emails

Hilary Stoupa — Wed, 13 Jun 2012 21:03:18 GMT

That's an odd one. Can you create a quick test form, see if the issue reproduces in another form? That is, try to see if the template is the issue?