InfoPath Dev

I have a form (2010) that works as intended. It has a button with a data connection behind it which emails the current form. Not as an attachment but with the current view in the body of the email.
I have since changed this to a filler form and all works fine except now the email is empty (except the introduction)... no view shows in the body of the email. No errors and no idea why.

help please!

You aren't switching views before the email is sent? That can cause this.

Nope, no switching.

Simple button action (button is enabled when 2 rules are satisified), when clicked it has an action to submit using the data connection

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?

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

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

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.

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

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...)

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"?

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.

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

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.

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

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.