Custom Transaction Form Validation

SuiteCloud Development Framework (SDF) includes the following validations for custom transaction forms:

The record type of the form is validated.
Several fields and attributes are required for custom transaction forms. For more information, see the reference documentation for transactionForm in SuiteCloud Development Framework XML Reference.
Components of the form are validated. For example, the validation checks whether the field ID is associated with a feature. The validation returns an error if a field is controlled by a feature that is not enabled in the target account. The validation log states that the fields are either invalid or do not exist in the account. If the feature cannot be enabled in the account, the fields must be removed from the custom transaction form.
When the default value for a field in the referenced standard transaction form is different between accounts, a validation error is returned. For example, the default value for a field is true in the referenced standard transaction form in source account but false in the target account. If the field value is read-only and must be included, the default value must be changed on the target account.
Some validation only occurs when the object is deployed to a target NetSuite account, and not when you validate the project against a target NetSuite account. The following examples cause errors on deployment:
- The original field has changed position. For example, the field has changed from top to bottom position.
- The original field was in the top or bottom position, and was moved to another tab.
- The original field is in the top or bottom position, and spaceBefore or sameAsPrevious were modified from their default values.
- There are changes to a custom transaction form that determine the availability of certain tabs. For example, the allowattachments field or enablemailmerge field of the custom_record_scriptid object cannot be changed to F when it uses the tab with the recordmedia ID.
For each role field specified in the transactionForm SDF custom object, the id field value must be for a role that has sufficient permissions for the transaction form.

For more information about resolving SDF validation and deployment errors, see SuiteCloud Development Framework Error Handling.

Additional information is also available in SuiteCloud Project Validation.

Related Topics