Support for Base64-encoded, Gzip-compressed stringsThis functionality has been requested by customers to solve real-world integration challenges. For example, eCommerce businesses can now extract shipping labels from Amazon Seller Central and bring better visibility to their Warehouse & Customer Support teams via other systems, such as an FTP server or NetSuite File Cabinet.
New connectorsBuilt-in connectors are now available for Mixpanel and SAP S/4HANA Cloud.
Revised connectors
Salesforce API version 52.0 is now supported – you can export and import newly introduced sObjects, such as Return Orders.
In addition, the Freshservice, Mavenlink, Miva, SAP Business ByDesign, SAP SuccessFactors, Shopify, and Square connectors have been updated according to the vendors’ latest APIs.
Additional extended characters allowed in requests
Universal HTTP connections now include support for ISO-8859-1 character set encoding in exported data.
-
When all records were filtered prior to a Snowflake lookup step, the connection would return an “uncaught exception” error
-
Syncing gift certificates from NetSuite to Salesforce Commerce Cloud would update the wrong item, due to a nlapiSubmitField function limitation for inbound shipment on custom fields*
-
In NetSuite custom forms with radio buttons, discount types were not populating flat and percentage values correctly*
-
Fixed-width files imported (uploaded) to Amazon S3 and FTP servers had “.edi” file extensions, regardless of the type chosen
-
Updates to Salesforce attachments generated the error “Unable to create/update fields: ParentId,” even though that field was not mapped
-
FTP exports set to a large batch size with an exceptionally large number of records produced the cryptic error “Cannot set property 'resolved' of undefined”
-
AS2 connections to HID Global partners would work as HTTP but not HTTPS
-
Cookies in redirected HTTP connections were not being passed through to the API, yielding an “exceeded maxRedirects” error
-
The handlebars helper {{hmac}} was not producing valid results in refresh token headers
-
The values in JSON number arrays were not formatted correctly
-
NetSuite Contacts and Contact Roles customer sublists were not available for exports or import field mapping*
-
In the Advanced field editor (AFE), if you started typing a field name, such as
record.E
for Email, and pressed Enter after typingrecord.
, autocomplete would begin the full path with your initial value, such asrecordrecord.Email
, instead of the selectedrecord.Email
as intended -
Field names containing a space would show up in the AFE autocomplete list only after typing
[
, instead of the expected initial letters
* This feature relies on the integrator.io bundle for NetSuite v1.19.1.0, which was released on October 19, 2021 and will be applied to customers’ Production accounts in phases throughout the following few weeks. The release is immediately available for Sandbox accounts, and you must manually upgrade the bundle in your NetSuite Sandbox Environment. (In compliance with NetSuite policies, Celigo cannot automatically update bundles in Sandbox accounts, only in Production accounts.)
Error Management 2.0 (EM 2.0) standardization for all accounts
Celigo will begin including EM2.0 by default for all new accounts. If you’re not already running EM2.0, you should become familiar with the improved error-handling capabilities and its new user experience.
Account-level dashboard for Error Management 2.0
In accounts upgraded to Error Management 2.0, you can use a new dashboard to:
-
View all flows that are still in progress or waiting in queue
-
View all flows that have completed within a specific time period
Deprecation of integrator․io legacy user interface (UI)
Since the current UI was introduced in 2020, there has been an option to Switch to legacy UI on the user avatar at the upper right of every page. Customers who were more familiar with that interface or, on occasion, unable to perform a task in the new UI had the option to continue developing integrations in the legacy UI. With this release, we are removing the option to switch back to our legacy UI, to mark the beginning of the final stage of legacy UI deprecation. If an issue is encountered where there is a need to switch back to the legacy UI, we strongly encourage you to file a support ticket, so that we can provide assistance with resolving the issue.
Parsed records include filename metadata
Each export that adds records to a flow’s data by parsing a file (such as XLSX or JSON) will also add a fileName field to that record. Then, you will be able to check that value later, making it easier to troubleshoot errors in the case where your flow contains records added from multiple source files.
The fileName was previously available only for “blob” files (downloaded in an export).
NetSuite listeners (real-time exports) built on SuiteScript 2.0
When you build a NetSuite listener , you can choose to set the NetSuite API version to SuiteScript 1.0 (using the current NetSuite bundle [20038]) or SuiteScript 2.0 (beta). Among other advantages, SuiteScript 2.0 offers faster bulk updates and better token security.
New connectors
Built-in connectors are now available for Freshservice, Looker, Omnisend, PandaDoc, Paylocity, OrangeHRM, PagerDuty, Quickbase, SAP ByDesign, SAP SuccessFactors, and Zenefits.
In addition,
-
A new Microsoft Azure connector is also available to handle binary large object (blob) storage
-
A built-in connector is now available for BrainTree; however, you must build the HTTP requests according to their API guide (a BrainTree “form view” is not available for flow steps)
New vendor-specific EDI templates
integrator.io is now able to export and import the following electronic data interchange (EDI) definitions:
-
Cardinal Health EDI 810
-
Cardinal Health EDI 850
-
Cardinal Health EDI 855
-
Cardinal Health EDI 856
-
Grainger EDI 856
New and enhanced templates
Since the last release, we’ve built a lot of great Marketplace templates for you to jumpstart your integrations, including:
In addition, some of the more popular Quickstart integrations templates have been updated with this release:
-
Orderful – NetSuite (updated to v3)
-
BigCommerce – Microsoft Dynamics 365 Business Central (updated to v3)
-
BigCommerce – QuickBooks (updated to v3)
-
BigCommerce – Acumatica (updated to v3)
-
BigCommerce – NetSuite (updated to v3)
Drag-and-drop transformation rules
Now you can easily reorder transform rules by dragging and dropping the fields just like you can when defining import maps. Simply create or modify a transformation, add transform rules, and rearrange the fields using drag and drop.
Usability improvements for identifying existing records
When you configure an import, the setting previously labeled Existing data ID is now called How would you like to identify existing records?. In addition, the available options and workflow for each option have been improved to streamline configuration.
More intuitive options for saving and closing
The buttons available at the bottom of each page have been updated to reduce confusion. The Save & close button now appears only if you have unsaved changes on the page, and integrator․io now indicates when saving is in progress.
Ability to sort and group content when using a file provider
If you export files that contain multiple rows for a single order, you'll want to check out the enhanced parsing capabilities in integrator․io. When creating or modifying a file provider transfer step, you can now set additional parse file options. The new options enable you to configure how records are sorted and grouped. You can specify one or more fields to use for sorting records and select the sort order. After sorting options are applied, integrator․io also applies any groups you have defined. When you define groups, you can specify one or more fields to use for grouping records together.
Error Management 2.0 enhancements
With this release, EM2.0 has become the standard, full-featured error-handling solution for all customers:
-
Migration path eased – Existing accounts can migrate without having to pause running flows. After migrating, you can retry any existing errors in a flow running EM2.0.
-
Fine-tune error resolution – You can now control which flows auto-resolve errors. Primarily, this feature allows you to disable Auto-resolve in cases where trace keys overlap and thus Auto-resolve might give false results.
Completely revised HTTP & REST API user experience
We’ve revisited and noticeably improved the usability in every setting (form field), as well as rewritten all of the help bubble () content, for each HTTP & REST API…
-
Connector
-
Export
-
Flow lookup step
-
Import
-
File transfer
These changes apply to the “universal” HTTP & REST API applications, as well as many of the options for built-in connectors to apps with these underlying technologies.
While you will notice more descriptive labels for the fields in existing flow resources – in slightly different groupings, all your current settings will remain unchanged.
Revised connectors
We’re continuing to improve the built-in API connectors and keep up with the providers’ features:
-
Amazon MWS – renamed Amazon Seller Central and beta support available for Amazon Selling Partner (SP-API) in the connection’s API type
-
Tableau – updated to v3.10
-
Freshdesk – additional endpoints added
-
Square – marked deprecated endpoints
-
Concur – added support for List v4; marked List v3 “to be deprecated”
-
HubSpot – includes support for Blog Authors, Blog Tags API, and Files API
-
3pl Central – now supports additional “PUT” endpoints
-
Shopify – migrated from version 2020-10 to 2021-07, with added support for 2021-07
BETA: Amazon Selling Partner API (SP-API) support
To transition from the planned deprecation of Marketplace Web Service (Amazon MWS) Orders, Reports, and Merchant Fulfillment Network (MFN) API endpoints, integrator․io is now enabling support for basic connectivity to SP-APIs.
Amazon SP-API is the next-gen suite of API-based automation functionality for Amazon selling partners, offering a number of improvements from Amazon MWS, such as modernized, JSON-based REST API design standards, OAuth 2.0 selling partner authorization using Login with Amazon, and a test endpoint.
NetSuite WSDL updated to include 2020.2
integrator․io now supports the latest NetSuite WSDL release (2020.2) along with all WSDL releases for the past three years. You can select the version when creating or modifying a NetSuite connection.
New listener Execution context
When creating a listener for NetSuite for a real-time export, you can now select “Web Application” as an Execution context.
Hat tip: Special thanks to active customer Lovesac for the feature request, as well as additional help with testing.
Customer-reported issues resolved
-
Removed multiple required API permissions from Microsoft Dynamics 365 CRM and SharePoint connector scopes
-
When certain flows in an integration were disabled, they would be relocated to Standalone flows without connections or mappings
-
Some flows with Amazon S3 imports would run until canceled
-
Okta connections to emea-okta.com were redirecting to the main okta.com domain
-
Administrator accounts were unable to register connections
-
Customers were unable to install integration ZIP files if they included a connection with the same name as an existing connection
-
In an Amazon MWS multipart/form-data import, the file was interpreted as XML, generated an error, and failed to upload
-
The AWS Lambda Stack region label for US West (Oregon) was mislabeled as [us-east-2] instead of [us-west-2]
-
ASCII characters entered in custom flow settings were incorrectly Unicode escaped
-
Field-specific qualification criteria filters on Salesforce webhook listeners generated parsing errors
-
Modified export (output) or import (input) filter operands were not refreshing when the field was changed
-
The Borrow concurrency from setting in a connection generated errors when reset to the default value (Please select)
-
Imports couldn’t be saved if there was a forward slash (/) character in the value for How should we find existing records? > Which field?
-
In rare occurrences, accounts that had migrated to EM2.0 had unexpectedly reverted to the previous error management interface
-
When cloning a flow, a single connection was applied to all NetSuite flow steps, and that connection could not be changed, even though alternate connections were required
-
In a free integrator.io accounts, the option to reactivate a flow was missing
-
FTP XML imports downloaded from the integrator.io dashboard were unexpectedly truncated and sometimes excluded data outside of the {#each} loop
-
Some real-time flow data (initiated by webhook requests received by integrator.io) were experiencing delayed processing
-
File transfer HTTP import data in the AFE 2.0 HTTP request bodyeditor validated as XML instead of JSON
-
The Handlebars editor interpreted Lookup URI data structures differently than how the data was processed during a flow run
-
The Build SOQL query editor did not correctly support {#each} handlebars loops
-
When exporting Salesforce opportunities, the records were not placed in descending order as configured
-
Flow steps in Flow Builder rendered incorrectly in the Safari browser on OSX
-
Mapping fields in the flow Salesforce Opportunity to NetSuite Sales Order Add/Update for the Salesforce – NetSuite Integration App (IO) prompted erroneous errors that had to be repeatedly closed
-
Order failed to add in Shopify: Could not find a match for itemID
-
Import Shopify orders in “Pending” payment status into NetSuite
-
Returnly – NetSuite (Nova Module) Integration app documentation
-
ShipStation – NetSuite (Nova Module) Integration app documentation
-
WooCommerce – NetSuite (Nova Module) Integration app documentation
The following articles have been added to Celigo integrator.io documentation:
-
Identify existing records when importing records from a data file
-
Enable NetSuite Assistant in Microsoft Edge or Google Chrome v91 and later
-
Set up an OAuth 2.0 HTTP connection to Azure Data Lake Storage Gen2
-
SAP Ariba Network – NetSuite template for Suppliers quickstart integration template
-
Salesforce Nonprofit – NetSuite Social Impact V2 quickstart integration template
-
Handle multiple transaction sets (ST-SE segments) in an EDI file
-
Microsoft Dynamics 365 Business Central – NetSuite quickstart integration template
-
Shopify - Microsoft Dynamics 365 Business Central quickstart integration template
The following topics have been substantially revised based on customer feedback, changes from this release, and ongoing quality efforts:
New vendor-specific EDI templates
integrator․io is now able to export and import the following electronic data interchange (EDI) definitions:
-
Target AU EDI 850
-
Target AU EDI 855
-
Target AU EDI 856
-
Target US (formerly “Target EDI”)
Marketplace tiles without templates or Integration apps no longer empty
The integrator.io Marketplace recently was upgraded to include a tile for every supported connector. In those cases where prebuilt integrations for the connector are not yet present, the category was empty. They now display next steps.
SQL query limit expanded to 128 KB
Some customers were negatively impacted by the previous limit of 32 KB. Expanding the limit to 128 KB resolves problems associated with large SQL queries.
-
All My APIs resources now include an identifier for their environment location ( Sandbox or Production)
-
Imports using FTP connections with PGP encryption and the BZIP2 format were not writing data
-
HTTP OAuth 2.0 connections to Bullhorn were not previewing export data correctly and were unable to refresh tokens causing the export to fail
-
NetSuite webhook exports that used nonexistent RMA numbers couldn’t be processed
-
Amazon S3 import backups were previously saving to a directory that combined the backup bucket name with the key prepended to the paths
-
BigCommerce lookups using the built-in connector would occasionally fail, unless the customer switched to an HTTP connection to BigCommerce
-
HTTP exports failed if the import destination could not use pagination
-
Handlebars expressions in HTTP POST submissions were not parsing correctly
View reports to audit records in a flow
A new Tools > Reports page allows you to analyze flow events – success, errors, and ignored items – to view the trace keys of the records that have been processed at each step.
Import mapping in one click
You can now automatically apply import field mapping between source and destination endpoints. integrator․io suggests corresponding fields for integrations between two applications such as NetSuite and Salesforce. Fields you already mapped are unaffected, and you can edit any of the mappings that have been automatically applied.
View logs for webhook
You can now set a “debug” timeframe to capture the requests received by integrator․io Webhooks. The data recorded will help developers in troubleshooting or investigating an error.
Single sign-on (SSO) authentication
Account owners and administrators can configure SSO authentication for integrator․io accounts to reduce security risks by providing increased assurance about a user’s identity. When the account owner enables SSO and configures it with the OpenID provider (such as Okta or OneLogin), users can securely access integrator․io without needing to store or remember usernames and passwords.
Then, account users can access integrator․io by clicking the app in the SSO provider’s web portal or browsing the SSO URL of the account.
PGP encryption/decryption
Improved PGP encryption settings are available for FTP, Amazon S3, and Google Drive, with added functionality to define compression settings and ASCII armor for the files. In addition, you can now enable or disable decryption (export) and encryption (import) for individual transfers that use a PGP-configured connection. The encryption settings also include an option to configure a signing hash.
Delete Salesforce records and files
When importing data to Salesforce, an added option allows you to permanently delete records and documents/attachments in your account that match the lookup criteria. You can also suppress errors for records that don’t exist when the flow runs. Previously, you would have had to establish an HTTP connection to delete records through the Salesforce API.
New connectors
Built-in connectors are now available for Fulfillment.com, Google Ads, Mavenlink, Walmart Canada, Walmart Mexico, and Yotpo.
New vendor-specific EDI templates
integrator.io is now able to export and import the following electronic data interchange (EDI) definitions:
-
Concordance EDI 810
-
Concordance EDI 856
-
Concordance EDI 855
-
Concordance EDI 850
-
GHX EDI 856
-
Max Warehouse EDI 832
-
Max Warehouse EDI 846
-
Max Warehouse EDI 850
-
Max Warehouse EDI 855
-
Max Warehouse EDI 856
-
Medline EDI 810
-
Medline EDI 850
-
Medline EDI 855
-
Medline EDI 856
-
Warehouse Quote EDI 940
-
Warehouse Quote EDI 945
New and enhanced templates
Since the last release, we’ve built a lot of great Marketplace templates for you to jumpstart your integrations, including:
-
PriceFx – NetSuite
-
Shopify – lexbizz
-
Amazon MWS – lexbizz
-
WooCommerce – lexbizz
In addition, some of the more popular Quickstart integrations templates have been updated with this release:
-
Concur – Acumatica (added expense report and payment request images)
-
eBay – NetSuite (new settlement flows)
-
Orderful – NetSuite (updated for Orderful v3 API)
-
BigCommerce – Microsoft Dynamics 365 Business Central (updated for BigCommerce v3 API)
Define a “trace key” for records
A record’s trace key is a unique field, such as an Internal Id, that identifies it throughout a flow. Error Management 2.0 (EM2.0) automatically resolves similar errors based on the trace key, and the record’s trace key is also retrieved when auditing flow data. In addition, it makes error records easier to search and identify.
The trace key is determined by integrator․io, but for a custom flow, you can override the value in the source app’s export or the destination app’s import in a one-to-many scenario.
Error Management 2.0 (EM2.0) enhancements
Customers running EM2.0 will have additional error handling visibility:
-
Complete HTTP request and response error information for integration steps connecting with an HTTP-based protocol
-
Enhanced error notification email layout to optimize viewing the error message on a small screen, including a link to view the export/import record (if available) in the source system
-
New metrics to see how many errors are resolved by customer interaction as opposed to Auto-resolved
Upgrade to EM2.0 to switch to a new paradigm in error handling.
Improved Business Process Apps Framework support
The built-in Business Process Apps Framework (a.k.a., Integration app framework 2.0) now includes support for edition-based Integration apps – allowing faster development and reduced maintenance of Integration Apps by app developers.
Remove partially installed integrations
When you begin to install an integration – from a Marketplace template, cloned integration, or a ZIP file shared with you – and then cancel, your integrator․io homepage displays the partially installed integration as • Continue setup. That often happens if you run into problems configuring the connection.
At any point you can click the integration tile to resume the setup. A new option in the installation page is Delete integration to remove the partially installed tile from your homepage to the Recycle bin. Previously, customers would have to delete the integration with an integrator․io API call or return to the Legacy user interface.
Filter by absolute number
Filters using the Number data type now support use of the absolute function to filter records on an exact number value.
Import mappings provide flow step context
When creating or editing field mappings, the title of the form includes the import that you’re working on, as a convenient reminder in case your flow contains additional imports.
Improved Advanced field editor (AFE) 2.0 experience
-
You can create lookups for the Relative URI setting of an HTTP import
-
Array-type fields shown in filter operands have a .length property
-
Flow group settings are available for transform and script editors
New connector options
We’re continuing to improve the built-in API connectors and keep up with the providers’ features:
-
Google Shopping – migrated from v2.0 to v2.1
-
integrator․io – EM2.0 error resource added
-
Shopify – migrated from version 2020-07 to 2021-04
-
eBay – filter format update
-
Walmart – renamed Walmart US
-
Wish – app removed pending update (connect via OAuth 2.0 universal HTTP)
-
Amazon Redshift and Google BigQuery – listed under Databases in Applications list
-
Orderful – v3 transaction endpoints added
Marketplace button gives clearer context
When browsing templates in the integrator․io Marketplace, the default action is now to Preview the template. Previously, the button read Install, which is a later step upon reviewing the template’s components.
QuickBooks API version settings expanded
Previously, flow steps to QuickBooks did not allow you to specify the minor API version. You can now include the full version as a query parameter.
SQL queries preserved when “Insert/Update” import operation changed
For all SQL imports (to MySQL, PostgreSQL, or MS SQL), any queries that you’ve entered for an Insert/Update operation will also be available if you change the selection to Insert or Update. Similarly, an SQL query that you type for an Insert operation or an Update operation will appear when you change the type to Insert/Update.
Customer-reported issues resolved
-
EM2.0 order import error notifications disappeared after a failed retry
-
Errors on records with identical trace keys were automatically resolved by EM2.0 without leaving access to the retry data or error messages
-
integrator.io was not storing retry data even when the Do not store retry data checkbox on the export was unchecked
-
Accounts with more than 1,500 flow steps did not display company logos and were unable to edit the flow steps
-
Creating a Data Loader export occasionally caused integrator.io to crash
-
Removed the Slack v1 API scope, remote_files:write, which if requested (or included with all scopes) would cause the connection to fail
-
Custom scripts no longer share resources between Sandbox and Production environments
-
Consecutive hyphens in Salesforce base URIs were causing connections to fail
-
Data Loader exports required a browser refresh to run more than once
-
Plain-text (not JSON or XML) API responses were not supported
-
In Salesforce – NetSuite Integration App v2, some NetSuite sublists displayed incorrectly
-
Failed FTP imports were not proceeding to the next step of the flow even when Proceed to the next application regardless setting was correctly configured
-
Encryption failed on AS2 connections and displayed passwords as plain text in debugged connections; the passwords have now been verified for basic auth type, and the connection details are masked in the debug logs as expected
-
Error notification email displayed oversized images in some email clients
-
Flow schedule override configurations were not triggering exports for multiple export flows
-
HTTP connection JSON structures were excluding subobjects
-
Integration app audit trails occasionally displayed the wrong account name
-
The list of standalone flows displayed duplicate entries
-
The Use SSL checkbox was not working for MySQL connections
-
When switching an export from XML to CSV, unnecessary HTTP response header values were retained, causing an error
-
Webhook records were sporadically processed twice and failed to import with a “!Page” error
-
Attempting to uninstall an Integration app a second time before it was removed led to a corrupted Integration app with a licensing error; the uninstall option is now locked until the operation is completed
-
Deleting integrations in the Sandbox environment failed when the Sandbox was disabled
-
Salesforce Opportunity sync criteria failed when applied to certain fields
-
Clicking a flow step option button (such as import mapping) wouldn’t work if the settings panel was already open
-
The eBay connector request URL was incorrectly formatted, causing connection errors
-
Update sales price for an Amazon item via pricing or product flow mappings
-
Get email error notifications on Salesforce – NetSuite v2 connector flows
-
Upgrade your Salesforce – NetSuite (IO) Integration App from standard to premium edition
-
Resolve permission error on the PayPal payout transactions flow
-
Change NetSuite connection from basic to token-based authentication (manual or automatic)
-
How to recognize a non-numeric NetSuite Invoice Identifier in a Sales Order
The following articles have been added to Celigo integrator.io documentation:
The following topics have been substantially revised based on customer feedback, changes from this release, and ongoing quality efforts:
New connectors
Built-in connectors are now available for Microsoft Teams, Adobe Sign, Authorize.Net, Freshworks CRM, Pipedrive, and PrestaShop.
New vendor-specific EDI template
integrator.io is now able to export and import electronic data interchange (EDI) definitions for Fifth Third Bank EDI 824.
Error Management 2.0 (EM2.0) Run history
After you opt in to EM2.0, you can view prior flow run results in a table format and download files processed in prior runs from all supported file servers.
Retry and Resolve errors action
EM2.0 error lists now allow you to perform bulk resolution actions on selected records (up to 1,000 records) or all matching records.
Auto-resolve
Auto-resolve (formerly called Autopilot) is now enabled after an account is migrated to EM2.0. If your accounts are already running EM2.0, then Auto-resolve will be added to your account to automatically resolve duplicate errors for you.
Enhanced encryption for NetSuite v2
NetSuite connections are now compliant with HMAC SHA-256 encryption, as required by the upcoming version 2021.2. (Older v1 connections in legacy integration apps have not been upgraded.)
Marketplace offerings better organized
Connectors are now sorted alphabetically in the Marketplace.
New NetSuite record type support
-
You can now update credit card refunds with Transaction record types on import into NetSuite
-
You can now use Purchase Contract record types for exports and imports
Connector updates
We’re continuing to improve the built-in API connectors and keep up with the providers’ features:
-
Integration app settings were not being preserved in the selected flow category when navigating between tabs
-
The Upgrade button would not display on the Subscription page for certain Integration apps in eu.integrator.io
-
The All-store view for Integration apps was not accurately preserving information when switched from the integrator.io Sandbox environment to the Production environment
-
Administrator-level users were allowed to migrate to EM2.0, which is now an option only for account owners
-
Handlebars expressions were not correctly evaluated in data exported from FTP, when the Advanced field editor v2.0 was enabled
-
In some cases, dynamic mapping was not correctly processing *.field values
JavaScript debugging
You can now view and print script logs – including info, debug, error, and warning messages – for each script in your scheduled flows. The new Scripts tab will be available in your flow Run dashboard for any flow that contains a script hook.
You can turn on debugging for a specified time frame. And the new built-in console object allows you to set properties and call methods to output informational events and resolved values at runtime.
Delete records & files for NetSuite imports
The NetSuite connector now supports deleting records and File cabinet files . You can configure lookup criteria for identifying those records or files that need to be deleted, with the option to Ignore missing records if none are found.
NetSuite authentication update
With the release of API version 2021.1, NetSuite does not allow new accounts to connect to a RESTlet via basic authentication. This auth type is now marked “To be deprecated – do not use.” If you’re still using basic authentication, you’ll need to change your authentication method to a more secure method, such as token-based.
Support for NetSuite contact role record type
integrator.io now supports the Contact role field on the Contact record type.
New account-level Administrator role
You can now assign all permissions granted to an account owner to any user who has access to your account. Previously, only account owners had the ability to invite users, manage user permissions, create API tokens, and perform other owner-level tasks.
New connectors
Built-in connectors are now available for Clover , Google Drive , Intercom , lexbizz , and PriceFx.
New and enhanced templates
We’ve built a lot of great templates for you to jumpstart your integrations, including Acumatica , ADP Workforce Now , Amazon AWS , Amazon MWS , Azure Active Directory , BigCommerce , HubSpot , Jira Cloud , Magento 2 , Mailchimp , Microsoft Dynamics 365 , Microsoft Dynamics 365 Business Central , Salesforce , SAP Ariba , SAP Concur Expense , SAP Concur Invoice , ServiceNow , Shopify , Slack , Square , Stripe , Zendesk Sell , Zendesk Support, and much more.
This is just a sampling of what you’ll find in the Marketplace! We’re putting out new templates all the time, so be sure to check it out!
New vendor-specific EDI template
integrator.io is now able to export and import electronic data interchange (EDI) definitions for Odyssey EDI 850.
Error Management 2.0 enhancements
When you’ve migrated your account to EM2.0, you can see the number of error retries and whether the retry has completed successfully or failed again. You can also filter the errors by the error source and timestamp.
Test more quickly in Dev playground
If you have Developer mode on, you can now launch a Dev playground editor with a sample file to start testing right away. You’ll now see subsections in each editor, offering different file types to use as input data.
Browse your resources in Dev playground
You can now view all of your integrations’ resources at a glance in the new tree view:
Click the links under Integration Explorer to open any resource throughout your integrations. The explorer allows you to copy and paste text that you’ve tested with the advanced field editors (AFEs) in Dev playground.
Context-sensitive connection setup help
When you’re creating a connection to an application, you can now click the connection guide link to walk you through setting it up.
Enhanced connectors
We’re continuing to improve the built-in API connectors and align with the providers’ features:
-
BigCommerce – Support for API V3
-
HubSpot – Added Search for contacts endpoint that allows you to search contacts by last modified date
-
Microsoft SQL – You can now choose 2008 R2 even though it is no longer supported by Microsoft
-
Orderful – Support for API V3
-
Shopify
-
Support for new API version 2021-01
-
Removed older versions 2020-01 and 2020-04
-
-
Target – Support for item taxonomy version 2
Improved connection debugging
When you start the connection debugger from the Connections tab in Flow Builder, you can immediately view the debug log. You can also clear the debug log history with a single click.
Enhanced handlebars helper
We’ve enhanced the timestamp helper in your handlebars statements to include the timezone using {{timestamp "DDMMYY" "US/Central"}} and other supported time zones. Note that the timezone used will be the one you have set on your own user profile.
integrator.io export data processing enhancementsWe've improved how we handle data processing in the export step of our platform to reduce the number of possible export errors during flow runs.
Improved sorting of resources in an integration
Flows, users, and connections are now sorted alphabetically by name instead of by last updated timestamp. This makes it easier for you to find flows and resources in lists.
Increased scope size for HTTP connections
In previous versions, new HTTP connections would test successfully, but if a large amount of scopes were selected, the connection might generate an error and go offline. We’ve increased the number of scopes allowed, to account for greater HTTP connection access.
Improved Integration App and template listing pages
For our partners, we've added more detail to these listing pages to make it easier to manage the integration apps and templates you create, including what applications each has, when it was last updated, and the website URL.
Customer-reported issues resolved
-
Environment field data now displays correctly for existing licenses
-
Fixed errors generated by the timestamp helper
-
For flows using the Zendesk connector, you'll now see the Refresh icon for import mapping and the Refresh metadata option in the Connections list
-
In import mapping, grouped fields (*.<field>) are now shown for Field export types of Lookup (Dynamic) or Multi-field mappings
-
Use first row option is no longer available for mapping types other than Standard
-
Output filters now properly identify negative values used for rules
-
Delta exports from NetSuite are no longer causing missing_start_date errors when running the flow
-
Salesforce attachment imports no longer display the option to ignore existing records
-
Token-based HTTP connections were not automatically refreshing tokens
-
DynamoDB no longer returns an invalid JSON error when the Export type is set to Once
-
Snowflake imports no longer return an error when the jsonSerialize handlebars helper is passed a field with a null value
-
FTP imports are no longer losing error retry data
-
NetSuite import script timeout errors are now properly reported when the flow is canceled
-
You should no longer experience exports’ freezing while editing them
-
Sandbox export previews from Salesforce Commerce Cloud should now be correctly displayed an S3 error when running in offline mode
-
When retrying errors in bulk, it will now correctly indicate status
-
In NetSuite integration apps, fields that were recently added to a Saved Search are now available for import mapping
-
Salesforce – NetSuite (IO) integration app updates:
-
Opening the field settings for the NetSuite Item Fulfillment to Salesforce Item Fulfillment Add/Update flow will no longer cause integrator.io to crash
-
When importing a large number of records, the cryptic error “unable to obtain exclusive access” has been revised with more meaningful instructions on how to avoid the UNABLE_TO_LOCK_ROW restriction in Salesforce
-
-
For Amazon and Magento 2 integration apps, locked list-level fields should now remain locked when adding a new mapping
-
Amazon Pay
-
Leverage multiple connections in your Integration App flow to improve throughput
-
Sync your NetSuite customer record via a mass update that uses a saved search
-
Authorize your Integration App connection to support Magento two factor authentication
-
Configure role-based permissions for Salesforce-NetSuite (IO) integration app in Salesforce
The following articles have been added to Celigo integrator.io documentation:
The following topics have been substantially revised based on customer feedback and ongoing quality efforts:
The following template readmes and support articles have also been published since the last quarterly release:
-
Concur Expense (Enhanced & Best Practice) – NetSuite Quickstart integration template
-
Concur Invoice (Enhanced & Best Practice) – NetSuite Quickstart integration template
-
Sync NetSuite refunds to BigCommerce from quickstart integration template
-
How to migrate QuickBooks Online to NetSuite for free with Celigo integrator.io
Comments
Please sign in to leave a comment.