1. SuiteCloud Platform
  2. SuiteCloud SDK
  3. SuiteCloud CLI
  4. SuiteCloud CLI for Node.js
  5. SuiteCloud CLI for Node.js Reference
  6. project:validate

project:validate

Validates the folder with your SuiteCloud project on the server.

By default, installation preferences aren't applied and account-specific values are ignored. Use --applyinstallprefs to apply installation preferences and --accountspecificvalues to specify how account-specific values are handled.

Syntax

            suitecloud project:validate [--applyinstallprefs] [--accountspecificvalues (WARNING|ERROR)]

Options

Option

Required / Optional

Description

--accountspecificvalues

Optional

Flags account-specific values as either a warning or an error. Enter WARNING or ERROR.

If you set the argument value is to WARNING and there are account-specific values in the project, you'll get a warning but deployment will continue.

If you set the argument value to ERROR and there are account-specific values in the project, you'll get an error and deployment will stop.

For more information, see Account-Specific Values Validation in SuiteCloud Projects.

--applyinstallprefs

Optional

Applies settings from the hiding.xml, locking.xml, and overwriting.xml files. If you use this option, the settings are applied; if not, they are ignored.

For more information, see Installation Preferences in the SuiteApp of SuiteCloud Project.

-i or --interactive

Optional

Runs the command in interactive mode.

-l or --log

Optional

Sets the deployment log file location, either as a directory or a file name.

If you specify a directory, a default log file is created in that location.

Important:

If a log file already exists in that location, deployment log details are added to the end of the file.

-h or --help

Optional

Prints the help for this command.

Interactive Example

Here's a command that validates your current project using the interactive mode:

            suitecloud project:validate -i

When you run the command, you're prompted to answer the following questions:

            Do you want to apply installation preferences? > Yes No
What do you want to do if the project contains account-specific values? > Ignore the account-specific values Display a warning Cancel the process

Non-interactive Example

Here's a command that validates your current project using the non-interactive mode:

            suitecloud project:validate --applyinstallprefs

Output Example

When you run the command, it produces an output that is similar to the following:

             
  >suitecloud project:validate -i
  √ Do you want to apply installation preferences? No
  √ What do you want to do if the project contains account-specific values? Display a warning
  VALIDATE SUMMARY
  Status: SUCCESS
  Steps: 18/18 successful
  Validation Results: 0 error(s), 0 warning(s)
  SDF Errors: none
  Local Timestamp: 2026-07-15T09:34:39.656Z
  Account: Wolfe Electronics
  Role: Administrator
  SuiteApp ID: com.netsuite.quarks
---------------------------------------------------------------------------
    Step 1: PROJECT_VALIDATION
    Step 2: MANIFEST_VALIDATION
    Step 3: DEPLOY_FILE_VALIDATION
    Step 4: CUSTOM_OBJECT_VALIDATION
    Step 5: CUSTOM_OBJECT_VALIDATION --- custcenter_sdftestframework_kyhd (center)
    Step 6: CUSTOM_OBJECT_VALIDATION --- custevent1 (crmcustomefield)
    Step 7: CUSTOM_OBJECT_VALIDATION --- custevent2 (crmcustomefield)
    Step 8: CUSTOM_OBJECT_VALIDATION --- custform_2_mstrwlf_330 (addressform)
    Step 9: CUSTOM_OBJECT_VALIDATION --- custinteg_d71c55db6be7 (integration)
    Step 10: CUSTOM_OBJECT_VALIDATION --- customlist10 (customlist)
    Step 11: CUSTOM_OBJECT_VALIDATION --- custpt_helloworldsuitelet (suitelet)
    Step 14: TRANSLATION_IMPORT_VALIDATION
    Step 15: TRANSLATION_REFERENCE_VALIDATION
    Step 16: PREFERENCE_VALIDATION
    Step 17: PLUG_IN_FLAG_VALIDATION
    Step 18: CIRCULAR_DEPENDENCY_VALIDATION

Related Topics

General Notices