![]() ![]() ![]() While you can compress TIFFs, most of the time they are uncompressed images. This means you can draft a PDF using macOS and it will look the same on a Windows PC, which is something you can’t always rely on when using other formats, such as DOC. PDFs are ideal for documents because they look the same regardless of the platform. Like a TIFF, a PDF can store multiple pages of a document. Meanwhile, a Portable Document Format file - or PDF - is used for storing and sharing digital documents. The format is very popular among photographers and graphic artists because it allows them to transfer multiple related images in one uncompressed file. It’s similar to other more common image formats, such as JPG and PNG, but differs in that it is capable of holding multiple images and sometimes even other types of files. I’ve wrote a separate post on how to overwrite files using the create file action, but basically the answer was to turn off chunking within the actions settings.A TIFF or TIF is an image file that contains one or many images. Overwriting existing PDF files causes flow to failĭuring testing of this flow I also noticed that when triggering the flow based off updating a site page, the create file create file action would error with a status 400 error saying “ A file with the name already exists”. I decided to scrap this approach and create a HTML page and add in the convert file action which worked around this issue. The flow also failed on this step and the error said that “Conversion of this file to PDF is not supported. In the file name I added ‘.PDF’, but every time the output PDF was corrupt and errored like this when trying to open: When testing this flow out I originally didn’t have the convert file action in place. Create file action creates corrupt PDF files The parse JSON action cleans this up and just leaves the body content of the page. Here’s the flow in it’s entirety: Issues & troubleshooting Formatting issues with the send an HTTP request to SharePointĪs mentioned above, when just using the send an HTTP request to SharePoint action, the output contains mark up that isn’t going to make sense within the PDF. This is reflected in the flow below with the condition step.ĭelete file action to remove the temporary HTML file. I set the default value of the choice column to be ‘Site Page’, so that the only pages that get converted are the ones I’m interested in. In my example I didn’t want all the site pages to be converted into PDF files, so I added a choice column to ‘tag’ all the pages that should be converted. A document library to store the output PDF files.A OneDrive location to temporarily store the SharePoint page outputs.A modern SharePoint site pages library (these come with every SharePoint site!).There are several posts online that cover very topic this that I’ll reference at the end, but they didn’t quite do exactly what I wanted – so here’s my take on how to convert SharePoint pages into PDF files! What you’ll need Also part of the brief was that when the SharePoint page is updated, the corresponding PDF file also updates. The converted SharePoint pages didn’t need to be formatted as it was only the body content of a SharePoint page that was needed. ![]() Recently I got asked to come up with a way to turn SharePoint pages into PDF files for use in an offline scenario. In this post we step through how you can use Power Automate to convert modern SharePoint pages into PDF files and save them to a document library. ![]()
0 Comments
Leave a Reply. |