Template by Microsoft Flow Community does not save

[teylyn1]

Hello,

I'd like to use the template https://flow.microsoft.com/en-us/galleries/public/templates/f9a2b550ebca11e6847527b0ccfd422d/copy-ne... to send new Outlook appointments to my Google calendar. 

I have added the connections to Office 365 and to my Google calendar.

When I save the template, it fails with the message "Flow save failed with code 'OpenApiOperationParameterValidationFailed' and message 'Input parameter 'newEvent' validation failed in workflow operation 'Create_an_event': The parameter with value '"@triggerOutputs()?['body/start']"' in path 'newEvent/start' with type/format 'String/date-no-tz' is not convertible to type/format 'String/date-time'.'."

What do I need to to to fix this?

[ChristianAbata]

hi @teylyn1  please could you give us an screanshot?

Solution gived by user

convertToUtc(triggerOutputs()?['body/start'], 'GMT Standard Time')

[ChristianAbata]

convertToUtc(triggerOutputs()?['body/start'], 'GMT Standard Time')

[teylyn1 · Accepted solution]

Found the solution. You have to wrap the time stamps into a ConvertToUTC function with GMT as the time zone. A bit weird, but it works.

convertToUtc(triggerOutputs()?['body/start'], 'GMT Standard Time')

[ChristianAbata]

@teylyn1 excellent please don't fotget to mark a post as a solution, to help others in the comunity.

[v-bacao-msft]

Hi @teylyn1 ,

Thank you for sharing!

I could reproduce this issue on my side. With the method you provided, this issue was resolved.

We could also get workaround from these links:

flow-save-failing-on-popular-template-due-to-obscure-date-format

office-365-calendar-to-google-calendar-2020-microsoft-flow

It seems that this is an issue with this template, we will report this issue to modified this Flow template so that other users could avoid this problem.

Thanks again.

Best Regards,

[vjpw]

Hi Team,

Where do you insert the logic to solve the error.

Could you explain me in the flow?

Best regards,

vijay

[Anonymous]

I've used this code and it works except it's an hour off (1 hr. early) my time zone. I enter the event in outlook O365 at 7:00 AM EST and it shows up in Google at 6:00 AM EST. Any ideas on how to fix it? I've been playing with different formats but can't seem to get it dialed in.

Thanks,

Nick

[sebaschaal]

I have the exact same issue...for me, I cannot get it to work for CET or CEST

[sebaschaal]

For now, I brute-forced it by wrapping the whole function with 

addHours()

So my start date looks like this

addHours(convertToUtc(triggerOutputs()?['body/Start'], 'GMT Standard Time'),1)

[summers]

I used this format and it worked out just fine. I had to build it and run it a few times, but it's working pretty well.

convertToUtc(triggerOutputs()?['body/start'], 'Eastern Standard Time')

convertToUtc(triggerOutputs()?['body/End'], 'Eastern Standard Time')

[stephendracup]

addHours(convertToUtc(triggerOutputs()?['body/Start'], 'GMT Standard Time'),1)

If I put this in the start time box for the google calendar - i get an error "Enter a valid datetime." below the start time box.

am I missing something?

[stephendracup]

Enter a valid datetime.

I get this error if I put your formula in the start time box for google Calendar 

addHours(convertToUtc(triggerOutputs()?['body/Start'], 'GMT Standard Time'),1)

am I doing this wrong?

[Anonymous]

I tried to use GMT time but in the way you're showing below:

addHours(convertToUtc(triggerOutputs()?['body/Start'], 'GMT Standard Time'),1)

But it always came back with an error - I was unable to use GMT with the correct zone for my time. The only I was able to make it work was using these 2 statements.

convertToUtc(triggerOutputs()?['body/start'], 'Eastern Standard Time')

convertToUtc(triggerOutputs()?['body/End'], 'Eastern Standard Time')

Not sure how else to get GMT to work with the corresponding time zone. 

[stephendracup]

addHours(convertToUtc(triggerOutputs()?['body/Start'], 'GMT Standard Time'),1)

Just worked it out - this needed to go in as Dynamic Content expression

so now I dont get an error - just need to test it

[Anonymous]

let me know if it actually returns the correct time on your calendar - I'd prefer to use the GMT statement you have. 

[stephendracup]

Yes it does. Not sure what will happen when the clocks change - but I now have it creating events in google calendar when they are nearly due. 

I will need to work on the logic to get the calendars to synchronise but now I have a method - shouldn't be too hard.

[DSteven]

Hi - I am trying to do the same thing, and have use the "add hours" code suggested in the Start time and End time boxes. It will Save but when I Test it, I get this error

The 'inputs.parameters' of workflow operation 'Create_an_event' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'newEvent/start' is required to be of type 'String/date-time'. The runtime value '"2020-11-03T13:30:00.00000002020-11-03T14:30:00.0000000Z"' to be converted doesn't have the expected format 'String/date-time'.

My Outlook calendar is on Central European Time and my Google calendar is on GMT. Any idea what I am doing wrong?

Thanks

[DSteven]

HI - I am trying to the same thing and have used the 'add hours' code suggested here in the Start time and End time box. It will Save fine but when I Test it, I get this error:

The 'inputs.parameters' of workflow operation 'Create_an_event' of type 'OpenApiConnection' is not valid. Error details: Input parameter 'newEvent/start' is required to be of type 'String/date-time'. The runtime value '"2020-11-03T13:30:00.00000002020-11-03T14:30:00.0000000Z"' to be converted doesn't have the expected format 'String/date-time'.

My Outlook calendar is on Central European Time and my Google calendar uses GMT.

Any idea what I am doing wrong?

Thanks

[DSteven]

This is the code I used in the Start time and End time box addHours(convertToUtc(triggerOutputs()?['body/Start'], 'GMT Standard Time'),1)

[stephendracup]

After the clock changed I am now getting my meetings created an hour later than they should be - is there another way of expressing GMT standard time so it actually returns the correct time (UTC+0)