Forum Discussion
Flow save failing on popular template due to obscure date format issue
Any advice will be appreciate with my similar error:
(a) Using Dynamic Content "Event Start Date Time"
Flow save failed with code 'OpenApiOperationParameterValidationFailed' and message 'Input parameter 'item' validation failed in workflow operation 'Create_a_Teams_meeting': The parameter with value '"@triggerOutputs()?['body/start']"' in path 'item/start/dateTime' with type/format 'String/date-time' is not convertible to type/format 'String/date-no-tz'.'.
(b) Expression1 convertToUtc(triggerOutputs()?['body/start'], 'GMT Standard Time')
InvalidTemplate. Unable to process template language expressions in action 'Create_a_Teams_meeting' inputs at line '1' and column '22105': 'The template language function 'convertToUtc' expects its second parameter to be a time zone matching the time zone indicated by the timestamp. The provided value '(UTC+00:00) Dublin, Edinburgh, Lisbon, London' is not valid or does not match the timestamp '2020-11-30T14:00:00.0000000Z'. Please see https://aka.ms/logicexpressions#ConvertToUtc for usage details.'.
Did you ever find an answer for this? I'm encountering the exact same issue
- lthomas138Jul 29, 2021Copper Contributor
I was experiencing the same issue. I resolved it by using the 'Convert Time Zone' action on my date field. I just chose the same time zone for both parameters but specified the format to be 'Sortable date/time pattern'. Then I was able to feed the output directly into my next step (Create Teams Meeting). Hope this helps you, too.
- Danyia_ZiaApr 13, 2023Copper Contributor
Where exactly did you add the convert time zone, I am having the same issue after adding this under my create event. lthomas138
- RandyH80Apr 17, 2023Copper Contributor
Danyia_Zia Here is an example of my flow:
The format start time is an expression,
formatDateTime(triggerOutputs()?['body/EventDate'])Convert time zone settings:Format string: Round-trip date/time pattern - 2009-06-15T13:45:30.0000000-07:00 [o]UTCUTC+1Keep an eye on the format string.Afterwards I did a new test with a positive result
- RandyH80Sep 02, 2021Copper Contributor
This is the solution for my problem, Thank you very much!
I think the conversion isn't working like as it should be because when I choose the correct source time zone, it just keeps adding the times to the original one form the calendar event. I have UTC+1, but when I left it to UTC+1 it just added 2 hours on the planning - not so good 🙂
The only thing that works fine is just reset it to UTC to UTC with no time zone selected, then it will keep the correct hour. Odd. Did you have the issue? (create event v4 for SP Online)
Br, R