You’re offline. This is a read only version of the page.
Announcements
Hi all,
New to Power Automate, but have finally created my first couple of flows. One of them looks like this:
Long story short - when a team lead goes into SharePoint folder and modifies an Update slide, a trigger happens where it converts to PDF, conerts to JPG, then placed in a seperate folder. That folder is connected to a Power BI report where the images poppulate.
Someone in another forum thread mentioned that because this trigger could be set of ALOT of times, I'd maybe have to consider some sort of Trigger Condition. Can someone please elaborate on what kind of trigger conditions you have used in the past?
And in this case, for a "when created/modified" trigger, what type of conditions are most common to make sure it doesn't run an absurd amount of times? When you open PowerPoint online through SharePoint, everytime that you're typing something in, or deleted, or really anything, you can see in the top left corner that it's constantly "Saving" or "Saved" meaning that it's constantly being modified as you go, which in this case isn't the best.
I'm using Plumsail as a tool to convert PPT to images, and I have a license that only allows 5000 per month. Now I don't think I'd hit this limit considering we only have 20 PowerPoint files in the folder, but regardless, what are some conditions you have used?
Share
Report
All responses (
Answers (
398
