GET SMARTER: (650) 579-0210

CloudExtend GContacts for NetSuite – February 2014 (Version 2.1.3)

  • Match criteria for sync changed from Email Id to Email Id and Name: The search criteria to sync contacts in previous versions has been Email Id match. However, its been noted that there might be quite a number of contacts with the same email id and the match is not always accurate.

    In this release, the match criteria has been changed to Name of the contact plus the Email Id of the contact to enable a closer match of Contacts in either systems.

  • Changed correlation of contacts in Google and NetSuite from many-to-one to one-to-one: In earlier versions of CloudExtend Contact sync, the application would sync all contacts with the same email id in Google to a single contact with a matching email id in NetSuite. This was causing data integrity issues whenever one of the Google contacts is updated.The 2.1.3 version of Contact sync application will now sync only one Google Contact to one NetSuite contact and vice versa at any point of time.

  • Queuing of contacts and retry of sync in case of sync failures: If a contact export or import sync fails, for example, due to Oauth token expiry reasons; the Contacts are queued up for sync and the sync process is retried every 1 hour until all the updated and newly created contacts are successfully synced.
  • Subsidiary of contacts in sync to not be auto-updated unless the field is empty: CloudExtend Setup module allows a NetSuite admin to set a Subsidiary as the default Subsidiary for contacts created/updated by Contact Sync application. When a Subsidiary was set as described, the previous versions of Contact sync changed Subsidiary field of all Contacts updated by the sync to the value mentioned in the Setup module.

    In this version of Contact sync, the application is made to update the Subsidiary field of a contact during sync, only on condition that it is empty. If a value is already entered into a Contact’s Subsidiary field, the application will not update the Subsidiary field during sync.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk