You’re offline. This is a read only version of the page.
I'm working on re-writing some old SP Designer workflows in Power Automate, and I've noticed some inconsistencies with how it handles all day events vs same day events aka calendar entries that only span a few hours.
I'm aware that SP stores its events in UTC time, so because of that I've seen people recommend using the Convert Time Zone action. This works great for same day events and my times are displayed correctly. For example, here is an entry that was submitted for 3/1 from 12:30 PM - 2:00 PM -
Item in SharePoint -
And how it came across in Power Automate -
However, all day events are not working correctly in this scenario. This is how the all day event appears in SharePoint -
And you can see that convert time is showing incorrect times for the start and end after doing the convert time zone -
Basically with all day events, in order to get the correct time it appears you do not need to convert the time zone. But with same day events, in order to get the correct time you do have to convert the time zone. Has anyone else run into this? I really don't want to have to create a condition and setup separate notifications based on if something is an all day event or not, so I'm hoping there is a better solution than that. Even if I wanted to go the condition route, I'm not sure how I'd do that as 'All Day Event' isn't an option within the dynamic content.
After some further research it looks like this is a known issue with all day events vs same day. I ended up creating different notifications for all day vs same day. As all day event is not available in dynamic content, I created a condition based on the end time of the event - if the end time contained 11:59, then I know it's an all day event.
Share
Report
377
All responses (
Answers (
