Custom Entry Forms as XML Definitions

Custom entry forms provide you with more control over how data is collected and entered. You can use custom entry forms to capture the information for a specific business application and to maintain consistency.

To find custom entry forms using the NetSuite UI, go to Customization > Forms > Entry Forms.


To work with entry forms in a SuiteCloud project, you must import custom forms from a NetSuite account.

You can edit the form that you imported and deploy the changes to your target account. To learn more about working with entryForm SDF custom objects and supported elements, see the following topics:

For information about all supported fields, attributes, and values, see entryForm in the SDF XML Reference.

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.

Related Topics

Custom Address Forms as XML Definitions
Custom Code Tab and Actions Tab in XML Definitions
Transaction Forms as XML Definitions
Sublists as XML Definitions
Subtabs as XML Definitions

General Notices