Enhanced Feature Dependencies for SDF Custom Objects
Your users can fully install an SDF SuiteApp when some of its NetSuite features are not enabled in the target account. If the account administrator later enables those features, the relevant SDF custom objects become available to your SuiteApp’s users.
This functionality is available for a limited subset of SDF custom objects for SuiteCloud Development Framework (SDF), which you can include in your SDF SuiteApp. Your users can install such SDF SuiteApps without encountering warnings or errors about missing features.
The following SDF custom objects support this feature dependency enhancement:
-
clientscript
-
customrecordtype
-
transactionForm
-
dataset
-
entryForm
-
itemcustomfield
-
othercustomfield
-
role
-
savedsearch
-
usereventscript
-
workbook
For information about enhanced feature dependencies in OneWorld accounts, see Enhanced Feature Dependencies for SDF Custom Objects Containing OneWorld Components.
Note the following information when including SDF custom objects in your SDF SuiteApp that support this enhancement:
-
SDF SuiteApp installation succeeds without any messaging to the user installing the SDF SuiteApp.
-
SDF SuiteApp deployment succeeds without any log entries outputted to the console of SuiteCloud IDE or the SuiteCloud CLI.
-
Validating a SuiteCloud project in SuiteCloud IDE or the SDF CLI does not notify you about features when they are not enabled in the target account.
-
During SDF SuiteApp installation, SDF custom objects that are restricted by features are created in the target account, but those objects are not visible until the feature is later enabled.
Uninstalling an SDF SuteApp also removes those SDF custom objects from the account, even when those objects were not visible.
-
You can still make the feature required for the target account by setting the feature’s
required
attribute totrue
in the manifest, even if you already used SuiteCloud IDE to add the dependency references for you. That attribute value ensures that the SDF SuiteApp installation fails when the feature is not enabled in the target account. To manually define the feature dependency, see Manually Defining Feature Dependencies in the SuiteCloud Project Manifest.Not specifying a feature in the manifest is functionally the same as setting the feature’s
required
attribute tofalse
.
The same functionality is also available for account customization projects (ACP) that contain supported SDF custom objects. The projects can be deployed to a target account that does not have the required features enabled. If the features are later enabled on that account, the SDF custom objects relying on those features will become available to that account’s users.
For all other SDF custom objects, the standard feature dependency behavior remains true. For information about standard feature dependencies, see Standard Feature Dependencies for SDF Custom Objects.