Hi All
New to Flow so be gentle if this is a "duh" question.
I'm taking a different approach to getting my O365 calendar onto my Google calendar (you can assume just authenticating and subscribing isn't an option). Creating new events in Google on the creation of new events on O365 is great if you're starting with a completely blank calendar, but that's not the case. Using ICS subscriptions seems to be updated by Google only every 12 hours or so and leveraging a combination of the two results in duplicate entries. In the hopes of a better option, I'm adding footer text to Flow created events so I can identify them to delete and recreate my O365 calendar to my Google calendar from a schedule for the next 90 days of activity. This eliminates duplicates, gets around the dreaded "deleted appointment" problem and puts me in control of the frequency of updates. Everything works as expected except.... Recurring appointments.
I'm using the "Start Time" to filter my list of calendar items to items starting between today and today + 90 days. What I'm experiencing is this:
I've read the posts pleading for a "recurrence" attribute for the Google Calendar connector so I know that's not an option. From my testing, I can assume that the "Start Time" on a recurring event is treated differently than on an event that is non-recurring.
Can anyone point me in a direction that will help me overcome my issue? Here's the relevant portion of my Flow.
Thanks
Ken
Hi @dugsdad,
This should be a current limitation of the Google Calendar Create Event Action.
I think you should noticed that there is no recurrence Input Box available under the Google Calendar Create Event action, and there are ideas submitted on this already:
Google Calendar Action Limits - Recurring Events
Add support for recurring Google Calendar events and delete triggers
Please vote it up so that the Product Team would then put its priority over the other feature requests.
Regards,
Michael
Thanks for the reply, Michael. I had already added my vote. 🙂 Was hoping someone may have come up with some creative workaround while we wait.
User | Count |
---|---|
89 | |
40 | |
23 | |
20 | |
16 |
User | Count |
---|---|
130 | |
50 | |
48 | |
35 | |
26 |