Limitations for Custom Transaction Forms

Consider the following things when customizing transaction forms in SuiteCloud Development Framework (SDF):

Configuring custom PDF layouts in SDF is not currently supported for custom transaction forms. To customize PDF layouts for custom transaction forms, see Customizing Transaction Form PDF Layouts.
Only supported custom transaction forms appear in the list when you are importing objects from a NetSuite account into your SuiteCloud project.
Identify fields that are not supported in target accounts and remove them.
Ensure that all dependencies are in the manifest file.
Renaming a form, and then deploying that form to an account that contains the original form, creates a new form. The original form is not overwritten by the renamed form.
Only Checks and Journal Entries contain the storedWithRecord element in the SDF custom object XML definition. The storedWithRecord element can be set to T or F. For more information, see Storing Custom Forms with Transactions.
When the original field is in the top or bottom position, the field's position cannot be changed, the field cannot be moved between tabs, and the default values for spaceBefore and sameAsPrevious cannot be modified.

Known Limitations of Custom Form Translations in SDF

The following are known limitations of custom form translations in SDF:

When exporting from your source account and importing a form into your SuiteCloud project, the button label values are not included for custom forms. Currently, translation collections do not support button labels.
To export to the SDF XML definition or import the SDF custom object into a SuiteCloud project, field labels must contain a value. If a field label has no value, validation of the SDF XML definition fails during installation. If you want to include a field that does not have a label, you can work around the SDF limitation by inserting a single space character as the translation for a field label. For example, you have fields for first name, middle name, and last name, but you only want a field label of Name to appear for the first field. You enter a label for the Name field and enter a single space for the other two fields.
Importing custom forms into SDF:
- When importing a form from the source account into your SuiteCloud project, the form translation is defined using the company default language, not the language of the user importing the form.
- When deploying a custom form using SDF, the target account receives the terms as they exist in the source account. If the target account does not have translations for the default language used in the source account, then the default language in the translation collection is used.