InfoPath Dev

 Hello, I have InfoPath 2013 and SharePoint online server 2013 plan E3. I'm trying to develop a way, when a webbrowser InfoPath form is submitted to the SharePoint server, an e-mail will be send to the submitter of that webbrowser InfoPath form with the current view. I developped something in SharePoint designer which works but the number of fields is limited. The webbrowser InfoPath form has more fields then SharePoint designer allows. Therefore, is there a way, when a user submits an InfoPath webbrowser form, he will have feedback of the data he submitted via e-mail?  With regards, Otto

Hi Otto,

 Have you tried creating a data connection that submits as an email message? With that method you can have your form both submit the web browser form and have an email sent out. First of all your going to have to make a field to input the user's email address(lets call that field Email). Next you'll have to create a new data connection that submits data as en email message > on the "To" field click the fx button then click Insert field or group and select your Email field > Add a subject if need be > Select whether you'd like the form sent as an attachment or just the view then click next > Name the data connection then click finish >  Lastly add an action rule to your Submit button that submits via data connection and select your email data connection from the drop down. Now when you click the submit button it will also email the form to the email address in your email field.

Hope that helps,

Mo 

Hello Mo, thank you for you responds. But I know the principle of working with e-mail connection on InfoPath. But then you will need InfoPath filler to read or change the form. My objective is to make the forms available for everyone, also those users which do not have InfoPath. Therefore the form must be a webbrowser based form, installed on a SharePoint site. This principle (sendig e-mail with InfoPath form to the submitter), after been submitted to SharePoint site, would work when I make the form full trusted and published it on a on premises SharePoint server. But this is the problem, I don't have an on premises SharePoint server but an online SharePoint server (plan E3). So, your solution will not work for me. With regards, Otto