In this guide you’ll learn how to convert InfoPath files to PDF using Power Automate. Converting InfoPath to PDF is a more involved process than other conversion types because InfoPath uses two files to create a single form, an XML (data) file and an XSN (template) file.
In this example, you will create a simple Flow that is triggered whenever a form is added to a folder in a SharePoint Online Library. Once this is added, the form is automatically converted to a PDF and stored in MS SharePoint folder.
This example can easily be adjusted to use different file services (e.g. the trigger can be for files uploaded to OneDrive, Box.com, DropBox, Google Drive or can even be used to Migrate your SharePoint On-Premise InfoPath Forms to SharePoint Online etc). A very detailed example is beyond the scope of this article.
Prerequisites
Before we begin, please ensure the following prerequisites are met:
- Make sure you have a Muhimbi PDF Converter REST-based API for Server Platform
- Make sure you have the appropriate privileges to create Flows.
Using PowerAutomate to Convert InfoPath files to PDF
From a high-level perspective, the Flow looks as follows:
Note: Converting an InfoPath form is similar to converting any other document type using Muhimbi's Flow Actions, but you will also need to pass in the XSN file (the file content, not the URL to the file) alongside the XML file.
This example takes you through converting a MS Infopath file to PDF. On a high level perspective, the steps to create are as follows:
Create a new Flow and use the SharePoint Online trigger ‘When a file is created’. Fill out the URL for the Site Address and select the relevant SharePoint folder.
Insert ‘Get File Content’ action and specify the path to the SharePoint Online location where the XSN has been published to. (By default it is stored in the Forms Folder, e.g. *‘https://yourdomain.sharepoint.com/sites/Sitecollectionname/Library/Forms/template.xsn’
Insert Muhimbi’s ‘Convert Infopath document’ action, and fill it out as follows.
Source file name: ‘File name’ the output from the ‘When a file is created in a folder’ trigger.
Source file content: ‘File Content’ the output of the ‘When a file is created in a folder’ trigger.
Output format: PDF
Template file content: ‘File Content’ the output of the ‘Get file content’ action, which contains the InfoPath XSN file.
View names: Enter the comma separated view names that needs to be converted to PDF
Include attachment: If you would like the attachments to also be converted to PDF, select Yes.
Attachment action: You can select how to deal with attachments. The options available are:
Default - If this is selected, the attachments are merged into the output file and unsupported attachments are removed.
Merge - If this is selected, the supported attachments are merged to the output PDF.
Unsupported attachments - If this is selected, the behavior will be according to the settings in InfoPathConverterFullFidelity.UnsupportedAttachmentBehaviour.
AttachAsPDF - If this is selected, supported attachments are converted into PDF and attached to the output document.
Unsupported attachments - If this is selected, the attachments are handled according to the settings in InfoPathConverterFullFidelity.UnsupportedAttachmentBehaviour.
AttachOriginal - If this is selected, all attachments are attached to the output document in their original format.
Unsupported attachment action: You can select what to do when the Converter encounters unsupported attachments. The default value is 'Error'.
Error - When this option is selected, an error is raised when unsupported attachments are found.
Remove - When this option is selected, the unsupported attachments are ignored and not included in the output.
AttachOriginal - When this option is selected, unsupported attachments are attached in their original format
Break merge on error: When you select ‘Yes’, then the merging of the document is stopped and an error message shown.
Default paper size: Select the paper size to be used if not specified in the view.
Default paper size (custom): Enter the paper size to be used if Default paper size ‘Custom’ is used.
Force paper size: Force the paper size to be used regardless of whether it is set in the views or not.
Force paper size (custom): Enter the paper size to be used if Force paper size ‘Custom’ is used.
Default page orientation: Select the default page orientation for the PDF.
Force page orientation: Force the page orientation to be used regardless of whether it is set in the views or not.
Start page: Select the first page to include in the PDF.
End page: Select the last page to include in the PDF.
Conversion quality: Select the quality of the output file.
Override settings: You can enter further optional settings using Muhimbi’s XML syntax.
Fail on error: When an error message is encountered, it will stop the process if ‘Yes’ is selected.
Note: Do not just pass the path to the XSN file into the Muhimbi Action as it doesn’t have the privileges to read that file.
Insert a ‘Create File’ action to write the converted file back to the OneDrive folder where the converted PDF files are written to. For the Folder path, specify the path to the OneDrive folder. For the File Name, pass in the 'Base file name' field returned by the ‘Convert Document’ action, along with '.pdf' suffix. In the File content field pass the 'Processed file content' returned by the ‘Convert document’ action.
You can write the converted file back to OneDrive folder, or Dropbox, or Google Drive, or you can send the PDF via email.
- Publish the workflow and upload a MS Infopath file in the specified document library. After a few seconds the Flow will trigger and a PDF file will be generated.
Please note that this is just a basic example. Muhimbi PDF Converter also comes with facilities to convert files attached to InfoPath forms as well as choosing which InfoPath view or views to convert. For more information, please feel free to contact our friendly support team.
