1
SOLVED! ~Bug: Creating a calendarEvent returns 201, but nothing is created~
Source: twentyhq/twenty#21619 · opened by @Bredo
Bug Description
When creating a calendarEvent with the REST API, I get a 201 created back, alongside a the new object.
I can also query that object by ID (find one calendar event), but if I search for it either by API or on the /objects/calendarEvents page, it doesn't show up.
Expected behavior
• That Create One calendar event is blocked if it's not surfaced - OR
• That manual calendar events can be searched and is shown as any other object entry
Feature request
I'll write a separate feature request later, on having "create calendar event" as a core capability, both as a logic function in workflows, as well as available in the SDK. This would likely be a "blind" create capability, awaiting the calendar platform to accept the change, and then propagate it with the standard polling
<img width="484" height="354" alt="Image" src=" />
When creating a calendarEvent with the REST API, I get a 201 created back, alongside a the new object.
I can also query that object by ID (find one calendar event), but if I search for it either by API or on the /objects/calendarEvents page, it doesn't show up.
Expected behavior
• That Create One calendar event is blocked if it's not surfaced - OR
• That manual calendar events can be searched and is shown as any other object entry
Feature request
I'll write a separate feature request later, on having "create calendar event" as a core capability, both as a logic function in workflows, as well as available in the SDK. This would likely be a "blind" create capability, awaiting the calendar platform to accept the change, and then propagate it with the standard polling
<img width="484" height="354" alt="Image" src=" />
No pledges yet. Be the first to back this.
Comments
Similar requests
Create new standard object Event
3 votes · 0 comments
Allow changing the display format of system date fields (createdAt and updatedAt)
0 votes · 0 comments
three issues on twentyhq/twenty, you pay only what merges
1 vote · 0 comments
Add regex pattern validation support for custom fields
1 vote · 0 comments
Use Company Icon as Opportunity Icon
4 votes · 0 comments
No comments yet.