This is where you select the specific example file (template) from step 1.Ĥ. Add a SharePoint action Get file content. Then I’ll have metadata about that customer that I can insert into the document, in the quick parts.ģ. I’ll just say, for example, that I have a SharePoint list of customers, and I’m going to select a customer and use the “for a selected item” trigger. So… you already have a trigger, I’m going to start with the first action. I’m not going to start with a Flow trigger here, there are many different ways you can start your Flow, such as when an item is first created, modified, or when someone manually triggers it. (If you’re coming from the SharePoint world where we’ve always done this with a custom content type, that method doesn’t currently work with Flow & modern SharePoint)Ģ. This file can be anywhere, it can be in a library by itself if you’d like.
If you followed the steps in the post about Flow and Quick Parts, use a blank file that has all of the quick parts already inserted. You need to have an example (template) file to start with. That’s what you see in Flow when you hover your mouse over the dynamic content, so that you can double check that it’s correct.ġ. You’ll notice in these screenshots, some small white text at the bottom.
Many times in business processes, this document needs to be output as a PDF file, in order to be archived or sent out to a customer.Ĭurrently in Flow, the only free way to convert a file to a PDF, is using a OneDrive for Business action, so the file can’t just be in a SharePoint library, it has to be in OneDrive in order to convert it, then it can be put back in SharePoint. Previously, I wrote a post called Microsoft Flow & Quick Parts, which shows how you can insert fields from SharePoint into your document via Flow and Quick Parts.
0 kommentar(er)
