NetSuite Changelog
SuiteCloud Development FrameworkSuiteCloudSuiteScriptCustomizationBest PracticesHow-To

Deploying Extensions: Key Processes in SuiteCloud Development

Understand the deployment process for custom extensions in SuiteCloud, crucial for maintaining your NetSuite environment.

·2 min read·View Oracle Docs

The deployment process for custom extensions in NetSuite involves several steps essential for maintaining your environment. When you deploy an extension, it is an upload process to your NetSuite file cabinet without any compilation or activation of files. This article outlines what happens during this process and how to prepare your environment effectively.

What Happens During Extension Deployment?

  1. File Copying: All custom extension files, including modules and assets, are copied into the DeployDistribution folder within your top-level development directory. If this folder does not exist, it is automatically created by the development tools.

  2. Code Validation: Before moving forward, the development tools validate your code to ensure integrity and compliance with standards.

  3. File Upload: The files are uploaded to your NetSuite file cabinet while preserving the original organizational structure of your development files. It is important to note that at this point, nothing is compiled or activated.

Important Note on Deployment Command

The command gulp extension:deploy is utilized to upload extension development files in batches known as chunks. By default, each chunk contains up to 80 files. You can adjust this number according to your needs. For troubleshooting, refer to the developer tools documentation.

Error Handling and Troubleshooting

During the deployment process, various issues may arise. These include errors related to permissions, invalid file assignments, and more. Some common errors encountered include:

  • Invalid Login Attempt: Ensure you have the necessary permissions.
  • Sass Compilation Errors: Check your Sass-related configurations.
  • Chunk Size Limitations: The chunk_size property in the gulp/config/config.json file dictates how many files are uploaded per request, which is bounded by SuiteScript's governance model.

It's crucial to reference SuiteScript governance limits during deployment, as the number of units each request can consume is fixed, and understanding these limits can aid in smooth deployments.

Frequently Asked Questions (4)

What should I do if I encounter invalid login errors during extension deployment?
If you face an invalid login attempt error, ensure that you have the necessary permissions set in your NetSuite environment. Check your user roles and permissions to verify that you are authorized to perform deployments.
How does the deployment command 'gulp extension:deploy' handle file uploads?
The 'gulp extension:deploy' command uploads files in chunks, with each chunk containing up to 80 files by default. This is controlled by the 'chunk_size' property found in the 'gulp/config/config.json' file, and you can adjust this number based on your needs.
Are there any specific permissions required for deploying extensions in SuiteCloud?
The article mentions that permissions are crucial during deployment, especially in cases of login errors. Ensuring that you have the required permissions configured correctly is necessary for deploying extensions.
Will deploying extensions impact existing compiled files or active processes?
No, the deployment of extensions does not impact existing compiled files or active processes, as nothing is compiled or activated during the upload process. Files are merely copied into the 'DeployDistribution' folder and uploaded to the file cabinet.
Source: What Happens When You Deploy an Extension? — 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 SuiteCloud Development Framework

View all SuiteCloud Development Framework articles →