Working with Non-SuiteCloud IDEs in NetSuite SuiteScript

Learn how to develop SuiteScript in non-SuiteCloud IDEs and manage script uploads effectively.

·2 min read·8 views·View Oracle Docs

Working with IDEs Other Than SuiteCloud IDEs allows developers to create SuiteScript files using various editors. While SuiteCloud IDEs are preferred for their integrated features, developing externally requires manual script uploads to the NetSuite File Cabinet.

Adding the SuiteScript Library File to Your IDE

To enhance coding experience in non-SuiteCloud IDEs, you can add the SuiteScript library file to your project. This enables features like code completion and improved syntax assistance. Only users with the appropriate SuiteScript access roles can download this file. Here’s how to do it:

  1. In NetSuite, navigate to Documents > Files > File Cabinet.
  2. Click the SuiteScript 2.1 API link to download the library file.
  3. Extract the files and follow your IDE’s procedure for adding external files to your project.

Uploading Scripts to the File Cabinet Without SuiteCloud IDEs

Upon enabling SuiteScript, a SuiteScripts folder is created in the NetSuite File Cabinet for script organization—though it's optional. Scripts can run from any location within the File Cabinet, but to effectively upload your SuiteScript scripts:

  1. Go to Documents > Files > SuiteScripts.
  2. Click Add File.
  3. In the popup, choose the desired file and click Open.

Key Guidelines:

  • Scripts must reside in the File Cabinet to execute.
  • When deploying a script for specific audiences (Customers, Vendors, etc.), select the corresponding role in the Audience subtab.
  • Ensure that any script or referenced files have Company-Wide Usage or Available Without Login enabled in their File Cabinet records.

To re-upload a modified SuiteScript file, repeat the upload steps and confirm by clicking OK to overwrite the existing file.

Who This Affects

  • Administrators: Managing SuiteScripts and permissions.
  • Developers: Creating and uploading scripts in NetSuite.
  • IT Teams: Ensuring compatibility of scripts with IDEs.

Key Takeaways:

  • Non-SuiteCloud IDEs can be utilized for SuiteScript development.
  • Manual uploads to the File Cabinet are required when not using SuiteCloud IDEs.
  • Script organization is enhanced with the SuiteScripts folder, but not mandatory.
  • Always check file permissions to ensure scripts run correctly.

Frequently Asked Questions (4)

Do I need specific permissions to download the SuiteScript library file in a non-SuiteCloud IDE?
Yes, only users with roles that include SuiteScript permissions can access and download the SuiteScript library file from the NetSuite File Cabinet.
What steps are involved in uploading SuiteScript files developed in non-SuiteCloud IDEs to NetSuite?
After developing your script in a non-SuiteCloud IDE, navigate to Documents > Files > SuiteScripts in NetSuite, click 'Add File,' and select your script from the file dialog to upload it to the File Cabinet for execution.
How do visibility settings affect the execution of SuiteScripts uploaded via non-SuiteCloud IDEs?
Scripts must have appropriate visibility settings, such as Company-Wide Usage or Available Without Login, configured in their File Cabinet records to function correctly across different roles.
Are there any specific steps to integrate the SuiteScript library into a non-SuiteCloud IDE?
Yes, you need to download the SuiteScript 2.1 API library file from the File Cabinet in NetSuite, extract the files, and follow the specific installation instructions for your chosen IDE to enable features like code completion.

Weekly Update History (1)

SuiteScriptupdated

Updated Setting Up Your SuiteScript Development Environment to show the new SuiteScript 2.1 library file link in the procedures.

View Oracle Docs
Source: Working with IDEs Other Than SuiteCloud IDEs Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in SuiteScript

View all SuiteScript articles →