When a date field is created or modified

[tdwils]

Hello,

I am trying to build a Flow that sends an email when a specific date column is either created or modified (we don't always immediately have a date in the column, but when we do I need it to recognize that change).  If it sees the change, it checks another field (has email been sent), then if that condition is true it waits until the day after the date in that field, sends the email, and marks the "email sent" field as yes (because I only need it to send once).

I am having an issue where it is not detecting changes.  I have changed the specified field date multiple times, but it always shows as false which stops the whole Flow in its tracks.  Any ideas?

[tdwils]

Bumping for visibility.

[v-xiaochen-msft]

Hi @tdwils ,

It's wierd. I can't reproduce the problem...

Could you share the error history screenshot of your flow? 

Besides, Is it because after sending the email, the "email sent" field is updated to 'yes' and the flow is triggered again?

Could you check flow and verify my guess?

Best Regards,

Wearsky

[tdwils]

@v-xiaochen-msft- so it's set to "yes" after the email is sent, but it's not even getting that far.  It's not detecting that I am making any changes.

It's technically not erroring - the Flow is succeeding but because it thinks no changes are being made, it's stopping.

Here are some additional pics:

I am changing the date over and over again in the SharePoint list, but no matter how many times I change, it is not recognizing that it's even changing at all.  I hope that makes sense!  Thanks for your help.

[tdwils · Accepted solution]

Hi all,

I managed to figure this out!  So, first off, instead of the expression in the "since" field, I just set it to "Modified."  This was enough to have the Flow detect the changes.  I also tweaked my condition, as I think there was another field that should have been using boolean terms (I also added a sub group to account for null fields).  Finally, I added a compose action before my delay, which was also causing issues.  Here is the final product:

[Evil353]

Hi

I had a similar issue. I resolved it by using "Trigger Window Start Token" in the *Since field.

 

Use the Condition function to set which field you want to monitor