Articles in this section

Zendesk-NetSuite release notes v1.10.0, February 2020

NoteWe’ve renamed our SmartConnectors to Integration Apps.

What’s Enhanced

NetSuite 'Suitelet' context added to Zendesk flows

We’ve enhanced the Zendesk - NetSuite IO Integration App version 1.10.0 to include Suitelet context to the following flows:

  • NetSuite Customer [Individual] - Zendesk User Add 
  • NetSuite Customer [Individual] - Zendesk User Update
  • NetSuite Customer- Zendesk organization Add
  • NetSuite Customer- Zendesk organization Update 

Previously, Zendesk Integration App updated Zendesk Id sync from Zendesk to NetSuite using the Suitelet context from the backend. The Suitelet context was enabled for flows that sync updates between the two apps. In such cases, the Zendesk Integration App would re-pick the update, sync it to NetSuite, and sync it back to Zendesk. This impacted the following flows:

  • Zendesk Organization to NetSuite Customer Add
  • Zendesk Organization to NetSuite Customer Update
  • Zendesk User to NetSuite Customer[Individual] Add
  • Zendesk User to NetSuite Customer[Individual] Update

You would have noticed multiple updates on records being made by the Integration App along with an increased number of success counts on your flows even if you hadn’t made any changes to your records. With the new Suitelet user interface change, you can turn on the Suitelet context from your flows. 

New timestamp field 

We’ve introduced a “Last Updated by Celigo” field that holds the value of the time when a record was last updated by the Zendesk flows. Whenever you run a batch flow from Zendesk, the flow picks up the “Last Updated by Celigo timestamp and compares it with Zendesk’s “updated_at” native timestamp on a customer record. If the difference between the two timestamps is between 3-5 seconds, we will not update the record. You also have the ability to offset the default 3-5 seconds time’s used as a qualifier for picking up a record to be synced. 

Limitations

The “Last Updated by Celigo” may sometimes return a timestamp older than the last created or updated timestamp. This is because of delays during the import process. The import process might get delayed due to:

  • Multiple parallel requests at the same time
  • Exceeding the API limit per minute 

By default, the Integration App considers a delay of 3 seconds. If the delay exceeds 3 seconds the Integration App picks the record in the reverse batch flow. 

You can customize this lag based on your environment and business needs via flow Mappings.

1.png
You’ll need to change the value for the timestamp expression in milliseconds as shown below:

2.png

New fields on NetSuite records

Additionally, we’ve introduced two new fields on your NetSuite customer records that are internally used by the Integration App:

  • “Skip export to Zendesk User”
  • “Skip export to Zendesk Organization”

Enable New fields in your Zendesk Integration App

New installs
You’ll automatically see the new fields after you install the Zendesk - NetSuite IO Integration App.

Existing Versions
We’ll be pushing updates to your existing Integration App install base for you. The updates include:

  • IO version v1.10.0.
  • NetSuite Zendesk Bundle version v1.9.5

New Users in Shopify trigger flows in Zendesk Integration App

The newly introduced Suitelet context also functions as an execution context. In other words, the Zendesk to NetSuite IO Integration App now syncs NetSuite Customers created by a third-party App to Zendesk Organisation. The most common use case is when you use Shopify, Salesforce, Zendesk Integration Apps to sync NetSuite Customers and Zendesk Users between these apps.

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.