Deleting Components in a SuiteCloud Project that were Deployed to a Target Account

The content and SuiteCloud project type affects the modifications you can perform using SuiteCloud Development Framework (SDF).

Components that are created in an account customization project cannot be uninstalled after they are deployed to a target account. You must manually delete the components from the target NetSuite account.

When a SuiteApp project is deployed to a target account, any object with the same application ID that already exists in the account and is not part of the deployment is deleted.

See the following table for details and exceptions when deleting components from a SuiteCloud project.

Action

Account Customization Project

SuiteApp Project

Deleting Files

Not Allowed

Files are not deleted in the account.

Partially Allowed

Only .js files are removed from the File Cabinet in the account when you deploy a SuiteApp project that does not contain those .js files. Other file types are not removed from the File Cabinet in the account when you deploy a SuiteApp project that does not contain them. For example, if you rename a file in the project and redeploy the project, the File Cabinet will now have two versions of the file.

Note:

If the SuiteApp is uninstalled from the account, files under the SuiteApps folder for that SuiteApp are deleted.

Deleting Instances

Not Allowed

Custom record type object instances are not deleted in the account.

Partially Allowed

Regular custom record type object instances are deleted when a new version of the SuiteApp project is deployed and it does not either contain the object or reference the object in the deploy.xml file.

Custom record type objects that are associated with custom segments behave differently. The instances are not deleted because this behavior would impact the GL.

Deleting Objects

Not Allowed

To help protect data in the NetSuite account, when you delete an object from an account customization project and deploy the project, the object is not deleted from the account. You must manually delete objects directly from the NetSuite account.

Important:

When an object is deployed to an account that contains a different type of object with the same ID, the object in the account is deleted.

Allowed

Objects are deleted when a new version of the SuiteApp project is deployed and it does not either contain the object or reference the object in the deploy.xml file.

Deleting Sublist Items

Allowed

When you delete a sublist item from an account customization project and deploy the project, only the sublist items in the project can exist in the account. Any sublist items that already exist in the account are deleted.

The permissions in the target account will not be changed or removed for role permissions that exist in the target account but not in the permission field group of the following SDF custom objects in the account customization project (ACP): customrecordtype, customsegment, customtransactiontype.

The permissions in the target account will be changed to the XML values for the permissions in the account customization project (ACP) for role permissions that exist in both the permission field group of the following SDF custom objects in the ACP and the target account: customrecordtype, customsegment, customtransactiontype.

Partially Allowed

Sublists or sublist line items are deleted when a new version of the SuiteApp project is deployed and it does not either contain the sublist or line item or reference the sublist or line item in the deploy.xml file. If there are existing line items defined in the account, they are retained.

If a SuiteApp is updated and it contains sublists without script IDs, only those sublist line items still included in the SuiteApp XML will remain. Existing line items defined in the account only are deleted.

If the entire SuiteApp is removed or uninstalled, the sublist and its line items are deleted from the XML and account.

The permissions in the target account will not be changed or removed for role permissions that exist in the target account but not in the permission field group of the following SDF custom objects in the SDF SuiteApp (or SuiteApp project): customrecordtype, customsegment, customtransactiontype.

The permissions in the target account will be changed to the XML values for the permissions in the SDF SuiteApp or SuiteApp project for role permissions that exist in both the permission field group of the following SDF custom objects in the SDF SuiteApp (or SuiteApp project) and the target account: customrecordtype, customsegment, customtransactiontype.

Deleting Subrecords

Not Allowed

Subrecords are not deleted in the account.

Important:

Exceptions can occur for the system to enforce uniqueness of an ID. When a subrecord is deployed to an account that contains a different type of subrecord with the same ID, the subrecord in the account is deleted.

For example:

  • When an existing workflow action has the same script ID as a new workflow action, and the workflow actions are under the same workflow, but the two workflow actions have different action types, the existing workflow action in the account is deleted prior to creation of the new workflow action.

  • When an existing script deployment has the same record type as a new script deployment, and both deployments are under the same script record, the existing script deployment in the account is deleted prior to creation of the new script deployment.

Allowed

Subrecords in the SuiteApp are deleted when a new version of the SuiteApp project does not contain either the subrecord or reference to the subrecord in the deploy.xml file.

Related Topics

General Notices