GET SMARTER: (650) 579-0210
Follow

GCal: CloudExtend Behaviour – Exception Case Scenarios

Optional Attendees

  • Case: Optional Attendees
  • Action: Create
  • Scenario: Event created in Google or NetSuite with optional attendees
  • CloudExtend Calendar Sync Behavior:CloudExtend will sync the optional attendees of this event to the other system as a Required Attendee in this release. This will be improved upon with migration to Google’s latest APIs

Multi-day events spanning across several days

  • Case: Multi-day Events
  • Action: Create
  • Scenario: Event created in Google over a period of several days
  • CloudExtend Calendar Sync Behavior:Since NetSuite does not support multi-day events, the event from google when synced will be divided into multiple events one for each day of the event period.

Editing a Multi-day event in NetSuite

  • Case: Multi-day Events
  • Action: Edit
  • Scenario: User tries to edit one of the multiple events in NetSuite synced from a multi-day event in Google
  • CloudExtend Calendar Sync Behavior:Edit on any of the multi-day events synced from Google is not allowed and an error is shown to user.

Deleting of Multi-day event in NetSuite

  • Case: Multi-day Events
  • Action: Delete
  • Scenario: Any one of the multiple events in NetSuite synced from a multi-day event in Google is deleted
  • CloudExtend Calendar Sync Behavior:All the events corresponding to the orginial multi-day event are deleted in NetSuite and subsequently the multi-day event in Google is deleted.

Multi-day event sync for different timezones

  • Case: Multi-day Events
  • Action: Create
  • Scenario: Time zone difference exists between NetSuite Company and Google User Calendar. Event is created in Google Calendar spanning over multiple days
  • CloudExtend Calendar Sync Behavior:Multiple events are created one per each day spanning over the entire duration of the event from Google. The splits in NetSuite are done based on the Company time zone of the NetSuite account and then converted to the NetSuite user calendar’s timezone. Note: In this case, it might be possible that an event in NetSuite is created where the End Time is earlier than the Start Time. This is a NetSuite Limitation. The user has to assume in this case, that the event ends at the End Time on the following day.
  • Example:Google Calendar Timezone: PST
    NetSuite Company Timezone: CST
    NetSuite User Timezone: PST

    An event is created in Google as follows:

    Start Time: 11/24/2013 8 am
    End Time: 11/26/2013 8 am

    Event is created as below in NetSuite:

    Event 1 of 4: Date 11/24/2013 Start Time: 8 am End Time: 1:59 am
    Event 2 of 4: Date 11/25/2013 Start Time: 2 am End Time: 1:59 am
    Event 3 of 4: Date 11/26/2013 Start Time: 2 am End Time: 8.00 am

Recurring events created on day of week with a timezone difference

  • Case: Recurring events
  • Action: Create
  • Scenario: Recurring Events created as follows in Google Calendar: Select Repeat, Monthly, day of week AND there is a timezone difference between the Google Calendar and NetSuite Company
  • CloudExtend Calendar Sync Behavior:Whenever the criteria is a weekday from the first or last week of the month AND there is a time zone difference that exists between the Google user and the NetSuite Company, the sync is only done when upon conversion into the NetSuite company timezone, the day of week condition remaiNetSuite same for all events in the destination recurring series. All other cases of recurring events are synced accurately.
  • ExampleNote: Unlike Google Events which can be specified in different timezones on one calendar, NetSuite allows creation of events only in the timezone of the user’s Calendar

    Google Calendar Timezone: PDT
    NetSuite Company Timezone: IST

    An event is created in Google as follows:

    Start Time: 10/31/2013 4 pm PDT (Thursday)
    Repeat Monthly By Day of The Week (Last Thursday of Month)

    Converting to destination timezone of IST this event series looks like:

    Source Series Event 1: Oct 31st at 4 pm PDT (Last Thursday of Month)
    Soure Series Event 2: Nov 28th at 4 pm PDT (Last Thursday of Month)
    Destination Series Event 1: Nov 1st at 4:30 am IST (First Friday of Month)
    Destination Series Event 2: Nov 29th at 4:30 am IST(Last Thursday of Month)

    In the above case, it is not possible to replicate the source series into destination coNetSuiteistently and hence the sync will not happen.

    However, in a case such as below, the sync will occur seamlessly

    Google Calendar Timezone: PDT
    NetSuite Company Timezone: IST

    An event is created in Google as follows:

    Start Time: 10/21/2013 2 am PDT (Monday)
    Repeat Monthly By Day of The Week (Third Monday of Month)
    Source Series Event 1: Oct 21st at 2 am PDT (Third Monday of Month)
    Destination Series Event 1: Oct 21st at 2:30 pm IST (Third Monday of Month)
    Source Series Event 2: Nov 18th at 2 am PDT (Third Monday of Month)
    Destination Series Event 2: Nov 18th at 2:30 pm IST(Third Monday of Month)

Recurring events created in Google after the 28th of a month

  • Case: Recurring events
  • Action: Create
  • Scenario: Recurring Events created in Google Calendar: Select Repeat, Monthly, day of month after the 28th.
  • CloudExtend Calendar Sync Behavior:Event is not synced to NetSuite as NetSuite does not allow recurring events on a date after the 28th of every month.

Recurring events of all types

  • Case: Recurring events
  • Action: Create
  • Scenario: Recurring Events of all types created in NetSuite regardless of existence of a timezone difference between the two calendars
  • CloudExtend Calendar Sync Behavior:Events are synced to Google Calendar and are created as per the timezone of the originating event.

Timezone change on Company Calendar

  • Case: Recurring events
  • Action: Create
  • Scenario: Events created on a weekly recurring basis in Google Calendar and the timezone of the NetSuite company is changed after the event is synced to NetSuite
  • CloudExtend Calendar Sync Behavior:The NetSuite calendar has a limitation of not being able to change a recurring event’s time accurately whenever the Company’s timezone is changed

Google events with Privacy Setting

  • Case: All events
  • Action: Create
  • Scenario: Events with Privacy Setting:Default/Public
  • CloudExtend Calendar Sync Behavior:All events with Privacy setting as Public/Default will be imported to NetSuite as a Public event. Private events in Google are not imported to NetSuite
  • Example:Note: This may change in a future update

NetSuite events with Privacy Setting

  • Case: All events
  • Action: Create
  • Scenario: Private and Show me as Busy events created in NetSuite
  • CloudExtend Calendar Sync Behavior:Private/Show me as Busy events created in NetSuite are not synced to Google

All day events with timezone difference

  • Case: All day events
  • Action: Create
  • Scenario: Create an All day event in Google or NetSuite. There is a timezone difference between the two Calendars.
  • CloudExtend Calendar Sync Behavior:All day events remain on the same date in both Calendars despite timezone difference between the two Calendars

Preferred form for imports into NetSuite

  • Case: All events
  • Action: Any action
  • Scenario: Event created/updated in Google. A preferred form is set for Imports in the Calendar wizard for CloudExtend Setup.
  • CloudExtend Calendar Sync Behavior:All events are created using the validation of default form and not the preferred form. If a user tries to edit the synced event on NetSuite, the preferred form’s validation rules apply. This is a limitation of NetSuite’s Calendar.

Event created by an external person

  • Case: All events
  • Action: Create
  • Scenario: An event is created in Google by an organizer who has a different domain than the licensed domain. The said event has attendees on the event who are from the licensed domain.
  • CloudExtend Calendar Sync Behavior:This event will sync to NetSuite, but will not sync the organizer information. The synced event will select one of the attendees of the licensed domain as the organizer of the event. Also, any updates to this event in NetSuite will not sync back to the original event in Google. All further updates from Google, however, will sync to NetSuite event.
Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk