Saltar al contenido principal

Domo University Videos

Domo

Connecting to NetSuite Data in Domo

Important: When referencing this page outside of Knowledge Base, use this link: http://knowledge.domo.com?cid=netsuite

Intro

NetSuite allows for data to be extracted via REST in JSON formats by accessing the endpoints as detailed below. The Domo connector expects JSON format, so all endpoints must include a parameter of format=JSON. The Domo Bundle uses the SuiteScript API (which is JavaScript-based) to extract data from Netsuite.

The connector has two components:

  • The Domo Bundle running inside your NetSuite instance

  • The connector code running in Domo

Primary Use Cases

This connector is great for extracting REST data in JSON format.

Primary Company Roles

Most appropriate for ERP/finance roles.

Average Implementation Time

4-8 hours

Ease of Use (on a 1-to-10 scale with 1 being easiest)

8

Configuration Instructions

  1. Download the following SuiteScript files.

  2. In NetSuite, go to Documents > Files > File Cabinet.

  3. Create a new folder inside the SuiteScripts folder named "Domo."

  4. Upload the two files (EC_Libs-4.0.0.js and EC_RestletDataExtractor.js).

  5. Go to Customization > Scripting > Scripts.

  6. Under File, search for and then select the script file (EC_RestletDataExtractor.js).
    A form now opens in which you can create the restlet.

  7. Fill out the form with the recommendations below (case-sensitive):

    Name = Domo Data Connection
    ID = _domo_data_extractor
    Script File = EC_RestletDataExtractor.js
    GET Function = EC.get
    Library Script File = EC_Libs-4.0.0.js

  8. Click Save and Deploy.
    You will now be taken to the Script Deployment center.

  9. For the Deployment ID, enter _domo_deployment.

  10. For the Status, select Released and leave the Log Level at Debug.

  11. For the Audience, please check Select All for Roles, Employees, and Partners.

  12. Ensure the Deployed checkbox is checked.

  13. Save and deploy the script.
    After the script is deployed it will present you with the Script Deployment status screen.

  14. Copy the External URL link for use in the next step.
    Once you complete the installation in the NetSuite instance, you will need to make the connection in your Domo instance:

    https://customer.domo.com/connectors/com.domo.connector.netsuiteApp

  15. Enter the following in the connector account box.

    Environment = Production or Sandbox
    Username = Your NetSuite username
    Password = Your NetSuite password
    Account ID = Your NetSuite account ID (Setup > Integration > Web Services Preferences > ACCOUNT ID)
    NetSuite Script Bundle ID = You will get this from the Script Deployment status screen.
    NetSuite Deploy Bundle ID: You will get this from the Script Deployment status screen.

    Once you have established the connection to NetSuite, you can now create DataSets from Saved Searches.

  16. Enter the Saved Search ID Number in Domo (e.g. for customsearch776, you would only enter 776).

  17. (Optional) You may also specify a date range using the Start Days Back and End Days Back fields. These fields calculate the days back from the current date.

    Note: When using values for the Start Days Back and End Days Back fields, you may end up with different results from what is displayed in NetSuite due to an additional level of filtering on the Last Modified Date field.

Useful Links

The following Netsuite document describes the SuiteScript API, which is what we use for the Netsuite connector. Specifically the chapter on RESTLets (chapter 22) pertains to our connector architecture.

https://system.netsuite.com/core/media/media.nl?id=5732122&c=NLCORP&h=5fca4bf5dd825a28ab41&_xt=.pdf&...

Limitations

Saved searches will never connect to NetSuite financial statements because of balancing entries that NetSuite doesn't expose in the saved search results.

Troubleshooting

  • If you get an "Unexpected Error" message after configuring the connection, check your column names for invalid characters such as apostrophes, quotation marks, backslashes, etc. 

  • Verify that the External Script URL, Script ID, and Deploy ID in NetSuite match what is in the connector.

  • Verify that the saved search ID in NetSuite matches what is in Domo and that it is the internal ID.

  • Verify that the saved search runs without issue in NetSuite.