I am connecting a flow to a SharePoint list with a field I labled "FollowUp" it is a calculated field based an entered End Date.
For testing purposes, I am trying to add a few minutes =End+1/24/30, when this date is used a flow delay until, I get this error. Is there a conversion I should be doing? (I want a followup email to be sent 2 days after the scheduled "End" Date.
BadRequest. The 'timestamp' value of the 'Wait' action 'until' inputs must be specified in UTC using the round-trip date/time pattern (for example, '2015-10-22T10:00:00Z'). For details please review the Standard Date and Time Format Strings of the .Net framework.
Per my certain knowledge, SharePoint Calculated column will return a Text value, while you are trying to use Date/Time value.
Please consider to use Workflow Definition language adddays function in your flow:
You could use a adddays function in a Compose action in your flow looks like below:
Please feel free if you need more help.
Thank you for offer to assist. I am not sure if I am using the adddays function correctly. For testing purposes, I am using addseconds to make my testing faster.
I am getting this error message in the flow:
InvalidTemplate. Unable to process template language expressions in action 'Delay_until' inputs at line '1' and column '2049': 'The string was not recognized as a valid DateTime. There is an unknown word starting at index 0.'.
I would suggest you use Compose action likes I mentioned before and use the Workflow definition language adddays. Then select the dynamic content of Compose action for Delay until field.
Please try it and feel free reply if you need more help.
The way I got around this was that I had a SharePoint column that took in a Date Only, used the Dynamic Content selector for it and added the Time format requested by the delay of T00:00:00Z. It looks like this:
This processed fine it seems. Feel free to use the 24 hour format on the time to adjust when you'd like the delay for. For the actual addition process you may want to try and get the more advanced @adddays() function to work, but this should fix the initial issue/error you were receiving.
Thank you for the additional information. Unfortunately, I am still get a TimeStamp error.
As you can see the calculated SharePoint column is Date Only. I do send an email from the Flow, and use the Follow Up date field. As you see in the Outlook email the Date field is Universal Time, not withstanding the column is "Date Only".
I would appreciate any further advise you may have to offer.
I just got this to work. I had to change the format of my field from Date Only to Date & Time. For some reason, Flow's "Delay Until" action hates date only fields. Even more of a pain since I'm using an InfoPath form template for the list. I hate these stupid pointless gotchas.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!