Differences Between SuiteCloud Projects
SuiteCloud Development Framework (SDF) supports two types of SuiteCloud projects: account customization projects and SuiteApp projects. These project types are optimized for their intended use. If you have never worked with a SuiteCloud project before, start with SuiteCloud Project Types.
SuiteCloud projects were formerly referred to as SDF projects.
The following table covers supported SDF actions for account customization projects and SuiteApp projects. Review these project type comparisons if:
-
You use both types of SuiteCloud projects.
-
You want more familiarity with expected SDF behavior.
For information about removing content after it is deployed, depending on project type, see Deleting Components in a SuiteCloud Project that were Deployed to a Target Account.
|
Action |
Account Customization Project |
SuiteApp Project |
|---|---|---|
|
Adding Dependencies to the Manifest |
Supported You can add feature, file, and object dependencies to the Manifest file. For more information, see Account Component Dependencies in SuiteCloud Projects, SDF Custom Object Dependencies in SuiteApps, and Feature Dependencies for SDF Custom Objects in SuiteCloud Projects. |
Partially Supported You can add feature dependencies and external SDF object in a SuiteApp dependencies to the Manifest file. For more information, see SDF Custom Object Dependencies in SuiteApps and Feature Dependencies for SDF Custom Objects in SuiteCloud Projects. Dependencies on files or objects that are native to the target account are not supported. |
|
Configuring Account Features |
Supported For more information, see Account Configuration from an Account Customization Project |
Not Supported |
|
Editing Custom Transaction Status from the NetSuite Account UI |
Allowed |
Not allowed A custom transaction status sublist is not editable in the UI if it is part of a custom transaction originating from a SuiteApp. |
|
Hiding Files |
Not Supported |
Supported For more information, see Installation Preferences in the SuiteApp of SuiteCloud Project. |
|
Importing Bundle Components |
Supported For more information, see Conversion of a Bundle to an Account Customization Project for SDF |
Not Supported |
|
Importing Files |
Supported You can import files into the account customization project from a NetSuite account.
Note:
The maximum file size of your SuiteCloud project (compressed as a zip file during deployment) is 50 MB. To maintain a small project size, you should use File Cabinet to upload large files and images to NetSuite rather than SDF. |
Not Supported |
|
Locking Objects |
Not Supported |
Partially Supported For more information, see Lockable SDF Custom Objects and Installation Preferences in the SuiteApp of SuiteCloud Project. |
|
Importing Objects |
Partially Allowed You can import objects that are native to the account and not installed by a SuiteApp. |
Allowed You can import objects that are native to the account or installed by a SuiteApp. |
|
Moving and Copying Files |
Allowed When you move files in an account customization project and deploy the change, SDF creates copies in the new location and original files remain in the original location in the NetSuite account.
Note:
Moving files in the project results in duplicated files in the target NetSuite account. You can manually remove the duplicated files from the File Cabinet. |
Allowed When you move files in a SuiteApp project and deploy the change, SDF creates copies in the new location, and removes the original files from the original location.
Note:
Moving files in the project results in deletion of the original files. |
|
Referencing Files |
Allowed You can reference files in the project or in the account. |
Partially Allowed You can reference files that exist within the same SuiteApp project. |
|
Referencing Objects |
Allowed An account customization project can reference objects in the same project, or objects in the account. The object must be declared as a dependency in the manifest file when from an account. |
Partially Allowed A SuiteApp project can reference objects in the project or in a SuiteApp installed to the account. |
|
Using Code Completion for File References |
When you specify a file reference from the IDE plug-in, SDF lists files that are present in the project and files that are defined as dependencies in the Manifest file. |
When you specify a file reference from the IDE plug-in, SDF can suggest only files that are present in the project. |
|
Using Code Completion for Script ID Attributes |
When you specify a script ID attribute from the IDE plug-in, SDF can suggest script IDs from objects present in the project and objects defined as dependencies in the Manifest file. |
When you specify a script ID attribute from the IDE plug-in, SDF can suggest script IDs from objects present in the project and objects defined as dependencies in the Manifest file. |
|
Validating Files |
Existing files in the project and files that are defined as dependencies in the manifest file are validated. |
Existing files in the project are validated. |
|
Validating Script IDs |
Script IDs from existing objects in the project and objects defined as dependencies in the manifest file are validated. |
Script IDs from existing objects in the project are validated. |
|
Re-deploying SDF Custom Objects |
SDF custom objects in an account customization project always replace the custom objects in the NetSuite account when you deploy, regardless of any previous changes made to those objects in the account. |
When you update a previously deployed an SDF custom object in the NetSuite account and re-deploy the same SDF custom object from a SuiteCloud SDK tool, the SDF custom object in the NetSuite account does not get updated. |