04-05-2018 16:48 PM - last edited 10-22-2018 08:58 AM
In this video Daniela (citizen developer extroadinairre) and I outline an effective approach to a common use case of providing critical documents to field staff using PowerApps. It utilises Flow to retrieve PDF from a central SharePoint document library and we also show how to improve the user experience via some clever but less known PowerApps and SharePoint tricks
Thanks for sharing this. Very good example of using PowerApps. My only note is about to use Flow. In a large organization with many users trying to get PDF info, how many times will be Flow called? this will affect, for sure, the kind of license you should get to avoid Flow issues, right?
This was immensely helpful! I was able to successfully set this up and display my PDFs, but when taking this one step further and exporting the PDF for the ultimate purpose of sending the PDF as an email attachment, I am wondering if there is a way to control the naming convention that is ultimately created for the PDF from the mobile device. From what I understand, PowerApps does not yet have the ability for me to send a PDF from the PDF Viewer as an email attachment (if I'm wrong and this is another flow I need to build, please let me know!). The workaround I am using is to export the PDF from the Viewer to a browser using the export feature, and then sending the PDF as an email from the browser. The file name is automatically named "Invoke.pdf", and I think this may be coming from the file path in Azure (part of the file path includes the phrase "invoke"). Is there a way to assign the file name through the current flow or a new flow?