Scheduling & Trigger Filters

The last module ties recurrence, data reshaping, and precise trigger conditions together — three separate skills Labs 6 and 7 each isolate on their own.

Recurrence triggers

A scheduled flow's Recurrence trigger fires on an interval you define — every day, every 6 hours, every Monday. Lab 6 sets it to run daily, but recurrence can also be manually re-run during testing via Test → Manually, without waiting for the real interval to elapse.

Data Operations: Select and Create HTML table

• Select — transforms an array of items into a new array with a different, simpler shape. Lab 6 uses it to pull just Task/Description/Due from a longer SharePoint item, and it handles the whole array at once — no loop required.
• Create HTML table — turns an array (like Select's output) into an actual HTML <table>, ready to drop straight into an email body.

A common trap: the designer sometimes auto-wraps a new action referencing an array output inside a For each loop. Select doesn't need one — it's already array-aware — so Lab 6 has you pull it back out.

Trigger filters — two layers

Automated triggers on Dataverse rows can fire far more often than you actually want to act on. Lab 7 narrows this down in two independent steps:

1. Select Columns — restricts the trigger to fire only when specific columns change, ignoring edits elsewhere on the row.
2. Filter Rows — an OData-style expression (e.g. statuscolumn eq 3) that further restricts the trigger to rows matching a specific value.

Together, these mean a flow watching for "opportunity closed" only wakes up when the status column changes and lands on the Closed value — not on every save of every opportunity.