The following differences exist between "old" Connectors or Integrations and "new" integrator.io-based Connectors and Integrations.
|integrator.io-based Connectors||NetSuite Integrator-based Connectors|
|Hosting Platform||IO Connectors are pre-built integrations that run native on the integrator.io platform.||NetSuite Integrator Connectors are pre-built integrations that run native on the NetSuite Integrator platform.|
|Installation Method||IO Connectors can be installed or uninstalled directly from the integrator.io marketplace.||NetSuite Integrator Connectors are installed into a NetSuite account via a SuiteApp (a.k.a. Bundle). These Connectors cannot be uninstalled from integrator.io; users must uninstall these connectors directly in NetSuite by uninstalling the SuiteApp.|
|Email notifications||IO Connectors support native email notifications from within the integrator.io platform.||NetSuite Integrator Connectors do not support native email notifications and users must use NetSuite Saved Searches to enable notifications for things like integration errors, connections going offline, etc.|
For new data flows built directly on integrator.io, the following applies:
|integrator.io Data Flows|
The “Add Submapping” feature is not currently supported in the integrator.io UI yet. This feature is used for data flows that need to import two separate record types at the same time and link them together. For example, it is very common for webstore integrations to import a customer and a sales order in one data flow, and the “Add Submapping” functionality allows one data flow to process a customer import first, and then process an order import and allow the order import to reference the customer that was just added.
In integrator.io, this is a feature that is currently being built and should be available in November. The temporary workaround for now is to use the integrator.io Hooks framework to write a small amount of code. Should you desire assistance with this, please contact Celigo Sales.
|CSV Upload to FTP site||
When exporting NetSuite data to an FTP site (in the form of a CSV file), integrator.io only provides a copy of the CSV file on the job record if the upload to the FTP site fails. If a CSV file is successfully uploaded to an FTP site (without any error) then integrator.io does not persist a copy of the CSV file on the job record. The main reason for this is to avoid the costs associated with persisting large amounts of unnecessary file data. It is only necessary to keep a copy for the purpose of retrying the upload when a CSV file fails to upload to an FTP.
Error messages will no longer automatically link to the NetSuite records being integrated via the Celigo Integration Log custom record. Saying this another way, in the NetSuite Integrator, all error messages were stored in NetSuite directly via a custom record called Celigo Integration Log, and because of this we were able to use NetSuite scripting functionality to auto display these records in a sublist on the NetSuite records being integrated. With integrator.io, we do not recommend viewing error messages in NetSuite and advise users to use the integrator.io dashboard and it's extensive error handling capabilities. We do provide links to NS records from the integrator.io dashboard if a user does want to click into NetSuite to fix a problem on a specific record. If a user really wants error custom records to be imported into NetSuite and linked to NetSuite records this would require a custom data flow be built. If you desire this functionality, Celigo may be able to enhance your io data flow to write back errors to a NetSuite custom record so that the errors can be viewed and reported via NetSuite. Please contact Celigo Sales to determine if this is possible for your specific integration needs.