I've seen one similar thread saying that the utcnow() only works in the condition field and you might need tog rab the current time from http://www.timeapi.org/utc/now as the current workaround. See here:
On your flow, you have a Update Item section to update your sharepoint list field. You cannot get today's date with that section. However, there is a workaround. Add another Update Item right after ths action. It will be named Update Item 2. Now you can access "Update Item"'s Modified. This field will be today's date.
But every time the list is updated this date will change. What if you need to capture the date a checkbox has been clicked but then end the workflow, like a Set Field, instead of Update Field?
I had a similar need to only perform an action if a condition were set to "Yes" (check box "Send Email"). The challenge is that if your trigger is a check box that is to be set to "Yes" in order for your flow to execute, then the flow will execute everytime the list is updated because the check box is set to "Yes." This you already know! Your spec for this flow is that it is to execute successfully only one time! My solution was to add another field to my list (Yes/No) defaulted to "No." This field is being used as a "trap" to capture the successful execution of the flow the first time. In my scenario an email is to be sent. Once the email has been sent by the flow I then update the "Trap" to "Yes" before the flow completes. Now I have the ability to "steer" the flow such that when any item is updated in my list, the flow "Tests" the "Trap" to make sure an email for that particular record has not been sent before. If the "Trap" is set to "Yes" the flow terminates. If it is set to "No" then it looks at the trigger check box "send email" to see if it is set to "Yes." If Yes the flow sends the email and then updates the "Trap" to "Yes" before terminating. If someone inadvertently switches the "Sent Email" checkbox back to "No" (which is possible because the list is used in a Power App) the flow will terminate because the trap has already been set to "Yes" preventing further execution.Bottom line you need two conditions, in your case a date change but then a post execution confirmation that the flow was successful. This structure for my flow uses more steps then necessary. I will modify this flow to incorporate a logic "And" to test for both conditions. As someone once told me when designing something new "Jsut get something that works on paper, it is easier to upgrade and enhance once something is working." "KISS" Keep It Software Simple!
Hope this helps. JK
I haven't had the time to try out this solution yet, my users decided to put the date in manually. it is still something I'd like to try for future use, butI'm sorry I don't have more to tell you 😞
Check out the announcement of Power Platform content at Microsoft Ignite!
Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.
Features releasing from October 2020 through March 2021