Creating an All Day Event in Outlook Issues

[SStockslager]

I have a need to create an All Day event based on the requested travel dates.  When selecting the event must be an all day event, adding start and end times to be T00:00:00Z (midnight) and it still errors out.  Please help me with the proper formatting for the Start and End time required for an All Day event.  Seems that I do not have it correct.

Thanks!

[abm]

Hi @SStockslager,

I tested with start date as 05/12/2016 00:00 and end date as 05/12/2016 23:59. It did worked correctly for me.

Thanks

[v-micsh-msft]

Hi @SStockslager,

What is your current situation?

I tested from my side, for creating All day Event, we could just omit the time part in Start Time and End Time input box, only keep the date, the folow process would add the time automatically.

Please take a try with this format and see if it would work.

YYYY/MM/DD

If you have any further questions, please feel free to post back.

Regards

[michowl]

@v-micsh-msft The problem with that solution is that the TimeZone is set to GMT by default.

I came up with a convoluted solution wherein I query 2 public TimeZone APIs.

1. https://timezonedb.com/references/get-time-zone gets the current timezone by lat,long (my flow is triggered by button)
   1. Returns a Unix timestamp
   2. TimeZone string is not compatible with Outlook
2. https://developers.google.com/maps/documentation/timezone also with lat long
   1. Requires a Unix timestamp as input (why I kept step 1)
   2. Returns a TimeZone string that Outlook accepts
3. I do some division and modulo on the timeZoneOffset from either of the TZ APIs above, and then use a convoluted string builder to create the TimeZone offset that DateTime wants
   1. TZHrs: div(int(body('HttTimeZoneDB')['gmtOffset']),3600)
   2. TZMin: mul(mod(int(body('HttpTimeZoneDB')['gmtOffset']),3600),if(less(int(body('HttpTimeZoneDB')['gmtOffset']),0),-1,1))
   3. TZFmt: concat('yyyy-MM-ddT00:00:00',if(less(outputs('TZHrs'),-9),outputs('TZHrs'),if(less(outputs('TZHrs'),0),concat('-0',string(mul(outputs('TZHrs'),-1))),if(less(outputs('TZHrs'),10),concat('+0',string(outputs('TZHrs'))),concat('+',string(outputs('TZHrs')))))),':',if(less(outputs('TZMin'),10),'0',''),outputs('TZMin'))
   4. StartTime: formatDateTime(addseconds(utcnow(),int(body('HttpTimeZoneDB')['gmtOffset'])),outputs('TimeZoneFmt'))
   5. EndTime: formatDateTime(adddays(addseconds(utcnow(),int(body('HttpTimeZoneDB')['gmtOffset'])),1),outputs('TimeZoneFmt'))
   6. TimeZoneName: body('HttpGoogleTimeZone')['timeZoneName']
4. In the Create Event, be sure to include TimeZoneName in both the start time zone and end time zone. You'll need to open Advanced and scroll all the way to the bottom.

It's messy, I know, but it works. It took me way too long to do this. Mostly because everytime I want to edit a Compose Action, I have to delete all its references and their decendents, then delete it, then recreate the whole chain. I'm putting in a feature request to be able to edit a Compose after it's been run. Some better math functions in the Workflow Definition Language would be helpful as well.