Then use a “Get file metadata using path” step to get any file by the same name from that library (use the “Name” dynamic content from the trigger step and add a. Create the second (optional) flow (delete. It starts out the same as our first flow, with a “when a file is added” step paired with a trigger condition but looking for. So we can create a separate flow to delete a. But it leaves the original file (.doc) behind which can be confusing for users. Any non-RTF file won’t be touched, and won’t trigger/count as a flow run. That’s it! Now when an RTF file is added, it’ll be replaced with a DOC version and the RTF file will be deleted. rtf file to avoid confusion – use Identifier from step 1/red) rtf contents – use dynamic data from step 2/blue) rtf file – use File name with extension dynamic data from step 1/red)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |