Status Update
Comments
mu...@google.com <mu...@google.com> #2
Hello there,
Thank you for reaching out. How would this feature request impact your organization in terms of costs and productivity? Are you currently using any workarounds for this?
ti...@gmail.com <ti...@gmail.com> #3
The workaround requires us to have a bot user logged in at all times who modifies the event from the calendar UI in order for it to propagate to all other guests. This feature would make our system significantly faster and less prone to error.
mu...@google.com <mu...@google.com> #4
Thank you for all the details. I have forwarded them internally.
Best regards
is...@google.com <is...@google.com>
dh...@gmail.com <dh...@gmail.com> #5
Are there any plans to fix this functionality?
ra...@gmail.com <ra...@gmail.com> #6
I'm looking for this functionality too, any updates on?
[Deleted User] <[Deleted User]> #7
lo...@gmail.com <lo...@gmail.com> #8
lo...@gmail.com <lo...@gmail.com> #9
lo...@gmail.com <lo...@gmail.com> #10
[Deleted User] <[Deleted User]> #11
Any update on this?
ka...@gmail.com <ka...@gmail.com> #12
Open Incognito Chrome window and go to the developer URL at top.
Select insert on the left menu
Fill out Try this method on the right (make the window wider if necessary):
calendarId = primary
sendUpdates = all
Request body =
{
"summary": "API Test",
"guestsCanModify": true,
"start": {
"dateTime": "2023-09-20T13:30:00-06:00",
"timeZone": "UTC"
},
"end": {
"dateTime": "2023-09-20T14:30:00-06:00",
"timeZone": "UTC"
},
"attendees": [
{
"email": "userAAA@gmail.com",
},
{
"email": "userBBB@gmail.com",
}
]
}
Click Execute.
Authenticate userAAA@.com
I get a 200 and "status": "confirmed" result.
Copy the id value to clipboard (or save the entire result somewhere).
Close the Incognito window.
Check Google Calendar for userAAA@gmail.com and userBBB@gmail.com on September 20, 2023 to confirm event created.
Open another Incognito Chrome and go to the developer URL at top.
Select patch on the left menu
Fill out Try this method on the right (make the window wider if necessary):
calendarId = primary
eventId = [the id saved from the insert event]
sendUpdates = all
Request body =
{
"summary": "API PATCHED",
}
Click Execute.
Authenticate userBBB@gmail.com
I get a 200 and "status": "confirmed" result.
Check Google Calendar for userAAA@gmail.com and userBBB@gmail.com on September 20, 2023
userAAA@gmail.com keeps the old summary: API Test
userBBB@gmail.com has the new summary: API PATCHED
The same problem occurs with other fields like start and end time.
You can change the event directly in Google Calendar as userBBB,
a popup will ask to Send Updates,
and the update will be reflected in Google Calendar of userAAA.
jp...@google.com <jp...@google.com>
na...@riley.ai <na...@riley.ai> #13
Any chance we can get an update from the Google team?
jp...@google.com <jp...@google.com> #14
I changed this to a bug and am escalating with the engineering team.
ap...@asana.com <ap...@asana.com> #15
Hi there - could we get an update from the engineering team on whether they are investigating this? This is preventing from building automation rules against the Google Calendar api that updates events for all users' calendars.
Without a fix, the user experience is not great. Thank you in advance
[Deleted User] <[Deleted User]> #16
dl...@google.com <dl...@google.com> #17
Dear all
Two options are recommended:
- Use the organizer's credentials to update the event. These are the credentials your application probably used to create the event
- If you don't have the organizer's credentials and want to update the event using the credentials of a guest with modify rights: make sure the guest has at least "free/busy" access to the organizer's calendar for the update to propagate to everyone's calendar.
Hope this helps!
mi...@vimcal.com <mi...@vimcal.com> #18
ha...@gmail.com <ha...@gmail.com> #19
I shouldn't need my coworkers credentials to edit the event when the permission set is configured properly.
mi...@vimcal.com <mi...@vimcal.com> #20
aa...@cactusflowerapps.com <aa...@cactusflowerapps.com> #21
pr...@mindy.com <pr...@mindy.com> #22
to...@gmail.com <to...@gmail.com> #23
Agree this is a severe bug, any updates from the Google Calendar team?
Description
A short description of the request:
Currently, when updating event details via the calendar API as a guest, the changes will only be reflected on your calendar and not the organizer/other guests. This feature request would allow you to also modify the "source" event that you were invited to. Of course, only if the organizer has the guestsCanModify boolean enabled for said event.
At the moment this functionality is supported by the calendar UI, however, I have not been able to find information on it regarding the API and it seems as though it's impossible.
What is the purpose of this new feature?
To allow accounts using the calendar API to modify events that they're invited to and that have the guestCanModify checkbox enabled.
Example:
What existing APIs would this affect?
The Calendar API update/patch endpoints
What existing data does this use?
Not applicable
Please provide any additional information below.
Similar to: https://issuetracker.google.com/issues/36757203