Hi, @VeeLearnMSFT ... not going to go super deep on this, as you'll get it as soon as you try some test events:
When a new response is submitted - This triggers on a new submission
- Get response details - This gets the details of the form
- Compose - Build an HTML page of what you want
- Create file - Make a literal HTML file from the above
- Convert file - Convert this into a PDF
- Create file 2 - Make a literal PDF file from the above
- Delete file - Delete the HTML file that was made
- Further logic
The above would fit in to whatever flow that you already have to point your Microsoft Form's entries into the SharePoint list.
Here's a VERY rough example of the last parts of that in action:
The result:
The Compose action should be reasonably customisable if you can work out what HTML is allowed in the conversion process. 🙂
However, you could replace the first 3 stages with a new SharePoint item trigger, and make an HTML table action the next one, put that in a page, and do the file stages.
At the end you choose what to do with the PDF, where to send it, save it, whatever, then you can delete that, too.
