Hello,
I tried to get into flow today and created a workflow (based on the online training) to approve vacations. It basically works fine but when I tried to add an automated Exchange calendar event as last step I hit a wall. The resulting event is not created/displayed correctly in Exchange - a two-day event is displayed as one-day.
The list item, where the value is based on, is formatted as Day/Time but of course without time, because the applicant shouldn't fill it in or even see it.
Another board topic here is about the same issue but the solution (implementing a Jquery into the Sharepoint List) seems a bit odd to me (and to be honest not applicable with my current knowledge).
Is there really no way (maybe with new Office 365 updates since that topic was created) that an Exchange all-day event can be created over multiple days?
My output currently:
Flow output
Resulting event (only 1 day)
Solved! Go to Solution.
Okay, of course a little while after I had almost given up, I found a solution 🙂
Through other posts I got a clearer picture about date operations and spaces in names of dynamic content in Flow. So, I tried to add a Compose action with an expression which adds 12 hours (to accomodate for any time zone hickups that could occur) to the end date of the vacation request.
addHours(triggerBody()?['Urlaub_x0020_bis'],12)
The date for a two-day event then is displayed correctly in Exchange.
I guess this has to do with some technical oddities in Outlook/Exchange - an all-day event that goes from Saturday until Sunday starts on the first day at 00:00 and ends on the third day at 00:00. So Flow simply creates the wrong date for the calendar entry.
Expression to add 12 hours
Use output from compose in event creation
Result in Outlook
Okay, of course a little while after I had almost given up, I found a solution 🙂
Through other posts I got a clearer picture about date operations and spaces in names of dynamic content in Flow. So, I tried to add a Compose action with an expression which adds 12 hours (to accomodate for any time zone hickups that could occur) to the end date of the vacation request.
addHours(triggerBody()?['Urlaub_x0020_bis'],12)
The date for a two-day event then is displayed correctly in Exchange.
I guess this has to do with some technical oddities in Outlook/Exchange - an all-day event that goes from Saturday until Sunday starts on the first day at 00:00 and ends on the third day at 00:00. So Flow simply creates the wrong date for the calendar entry.
Expression to add 12 hours
Use output from compose in event creation
Result in Outlook
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
User | Count |
---|---|
45 | |
42 | |
36 | |
36 | |
22 |
User | Count |
---|---|
41 | |
31 | |
29 | |
28 | |
26 |