With the August 2020 release of CloudExtend Outlook for NetSuite we moved to an improved asynchronous attach flow that allows users to get back to work in Outlook faster. This attach process also made several improvements to the file attach process.

This approach requires a connection to the customer's Exchange REST API. For the vast majority of users this is not an issue.

In order to ensure backwards compatibility for our customers that do not have access to the REST API we have added a setting to revert back to the legacy attach method.

Enable the legacy attach

To enable this setting navigate to the menu (3 dots at top right) and click settings, and the click 'Developer Settings' and enable the legacy file attachment by clicking it.

What happens when I enable legacy attach?

When legacy attach is enabled users will move back to a synchronous attach process for emails and the files will be added to a queue. This means that after clicking 'attach' the user will need to wait 2-5 seconds for NetSuite to attach the email before moving on with their work. The files will then go into a queue and will appear on the email attachment with a prefix of 'Uploading....'. Once the upload is complete the file name will replace 'Uploading'.


There are many reasons to use the REST API now and in the future. Most of our customers simply subscribe to Microsoft and have Microsoft host their email through a Microsoft 365 subscription. With this approach you are always on the latest version of Exchange and you can let Microsoft deal with the updates.

If you have your server hosted or on premise please work with the folks that manage it to get updated.

Other Notes

If you fix the REST API issues and disable the legacy file attach setting the previously attached records would not be visible in the add-in. However, the message will still be marked with an "Attached to NetSuite" category and the message will still remain in NetSuite.

Did this answer your question?