Convert Infopath 2010 browser enabled form to PDF when Submiting. Hi all, Im having a infopath form browser enabled form. I need to sumbit it to a document library.

Hi, I am pulling my hair out on that one. How can I convert an InfoPath form which has been created, then approved, to a MHT or PDF through a Workflow? I have tried Muhimbi but the InfoPath feature is in experimental mode and doesn't work on with my form. Muhimbi works great on any word, excel, etc. But just stall on this InfoPath document. A MHT version of my InfoPath would make it (or PDF).

The client side 'Save as. MHT or PDF' is great. Could that be automated on the server side and used through a workflow? Task to perform: =========== 1) InfoPath Document status is changed by user to 'approved' =>trigger Workflow. 2) Workflow does a 'Save As. MHT or PDF' of that current InfoPath and put that converted version to a new Library.

Sounds easy on the paper. But I can't figure out how to do that. Any help would be appreciated. Best regards. Paresh, Thanks for the answer. I don't think it answers my question.

I had seen these posts before asking this question. I posted this question on the Infopath bulletin board, I could have also posted it on the Workflow bulletinboard. Your 1st link describes how to call the click side Export to PDF Add-in. Your 2nd link describes also how to do it on the client side. Your 3rd link describes how to convert the HTM form of an Infopath to be exported to PDF through a button. What I am looking for is a Server Side automated solution. So I can trigger the conversion through a Workflow in Sharepoint.

This workflow would be triggered from a different list than the Document Library holding the InfoPath file. So the quest is still on;-) If someone else has a solution, I keep my ears open. Best regards. Paresh, Thanks for the answer. I don't think it answers my question.

I had seen these posts before asking this question. I posted this question on the Infopath bulletin board, I could have also posted it on the Workflow bulletinboard.

Your 1st link describes how to call the click side Export to PDF Add-in. Your 2nd link describes also how to do it on the client side. Your 3rd link describes how to convert the HTM form of an Infopath to be exported to PDF through a button.

What I am looking for is a Server Side automated solution. So I can trigger the conversion through a Workflow in Sharepoint. This workflow would be triggered from a different list than the Document Library holding the InfoPath file. So the quest is still on;-) If someone else has a solution, I keep my ears open. Best regards Actually, the 3rd link does not convert the HTM of an InfoPath form and exports it to PDF. I wrote the article myself, so I'd know.:) If you scroll down and take a closer look at listing 4, you'll see that what it actually does is take the XML of the InfoPath form, navigates it to find nodes and values, and then uses these along with the object model provided by iTextSharp to construct a PDF document.

You can do the same thing in your workflow without the need to press buttons. If you want to know how to retrieve InfoPath form data in a workflow, see.

Blog posts and articles are not meant to provide you with a final solution; I doubt you'd find the solution you're after online. However, you can take bits and pieces from each blog post or article to put your own solutions together. So what you're after can be done; you just have to extend the concepts. Wong-A-Ton, (100+, tutorials, and solutions).

I have built an InfoPath Filler form that I deployed to a SharePoint 2010 Form Library. While deploying, I checked that the form could be opened up using a web browser. I receive a warning that the form template has been published to the server but if can only be opened in InfoPath Filler. This is a problem, because it was decided that the form would be required to be opened using the browser. I made changes to the form so that it abided by the rules which allow it to be opened using a broswer (There were no design checker warnings or errors). This is the second form that had this problem. To fix it the first time, I simply created a new form that was not a filler form.

Now that it has happened again, I wonder if there is a way to convert the filler form to a web browser form to save development time. Can this be done? Any other suggestions?

Scenario Using SharePoint 2010 and Infopath web browser admin approved forms. I have a big form that will take serveral edits over time via collaboration between two users prior to submission.

I use two form libraries say WIP for work in progress and Submitted for submitted forms. There are different access permissions to the two libraries.

When a user submits a form from the WIP library to the Submitted library I want to set a flag on the WIP form to say submitted=Yes so that if they go back into the original WIP form they cannot submit a second time with the same form. I use this flag field to set a read only view of the form. Gebruder Monnig Serial Numbers there. The trouble is that when I set the flag before triggering the submit then the flag is set but the current form is not saved before it is submitted as a new form to the submitted library so the flag never gets set on the current form! Ideally I want to force a save to the WIP form immediately prior to a submission but after I set the flag field value. I am having difficulty in finding out how to do this - any suggestions? I realise that submit is a form of save but I want to simply save the current form as part of the submit action. What is happening is that the form is submitted to the other library but THIS form is not saved.