ExtendSync for Google Calendar supports bi-directional synchronization of recurring events, including exception-based changes, between NetSuite and Google Calendar.
This article explains how recurring events are handled and how exceptions to those events sync between both systems.
How Recurring Event Sync Works
When a recurring event is created in either system:
The recurrence pattern (daily, weekly, monthly, etc.) is synced to the other system
The event series maintains the same recurrence rules in both NetSuite and Google
Changes to the overall recurrence pattern sync bi-directionally
This behavior applies to supported calendar events managed by ExtendSync Google Calendar.
What Is an Event Exception?
An event exception is a single occurrence within a recurring series that differs from the original recurrence pattern.
Common examples include:
Skipping one occurrence
Declining a single instance
Rescheduling one meeting in a recurring series
Modifying details (time, title, location) for a specific occurrence
Example
A weekly status meeting occurs every Friday at 3:30 PM. If you decline or reschedule only next Friday’s meeting, that individual occurrence becomes an exception to the recurring event.
How Event Exceptions Are Synced
Supported Behavior
ExtendSync for Google Calendar syncs event exceptions:
From Google Calendar → NetSuite
From NetSuite → Google Calendar
This includes:
Declined instances
Modified single occurrences
Deleted occurrences within a recurring series
Only the affected instance is changed; the rest of the series remains unchanged.
Best Practices
Modify the series when you want changes to apply to all occurrences
Modify a single instance only when an exception is intended
Avoid making conflicting edits to the same occurrence in both systems at the same time
Test recurrence behavior with sample events before large rollouts