Power Platform Community Forum Thread Details

I am trying to create a workflow from a SharePoint list to a Planner Task. The problem I am bumping into is that the trigger I'd like to leverage is from a calculated field. Below are the two options I'm interested in - I'd be willing to go with whichever is easiest, but the calculated field is giving me problem (at least I think that's where the problem is).

Option 1:

Once a day, review the SharePoint list
Condition: If any items on the list are at 300 days since last review (the days column is the calculated field), create a planner task
If possible, then send an email advising how many new tasks created that day (this part of workflow is not critical)

I've tried it both ways and it's not creating my planner tasks.

Option 2:

Trigger: If days since last review are at 300 days (calculated field), trigger creating a planner task
If possible, once daily send email summary with how many new tasks created that day (this part of workflow is not critical)

Categories:

Building flows

Hello @jessfulks ,

calculated fields are a problem, you shouldn't use the column directly, you should move the calculation into the Power Automate flow. You can't trigger a flow based on such condition, you'll need the option 1, a scheduled trigger.

Then, in the flow, instead of checking if the calculated column has number 300, you can use Power Automate expression to achieve the same result. Check if today is 300 days from the review date, in form of a Filter Query:

LastReviewDate eq 'addDays(utcNow(),-300,'yyyy-MM-dd')'

that means LastReviewDate is equal today-300 (300 days ago)

Notes:
LastReviewDate is internal name of the SP column, it should be a date only column
addDays(...) is an expression

I wrote also an article on replacing calculated column with an expression if you're interested.