Custom Transaction Form Format
SuiteCloud Development Framework (SDF) requires the following format for custom transaction form objects:
-
XML body fields or elements in forms must follow the order as exported.
-
A field can be deleted if it is not required.
-
Field order can only be changed within the same position. Field position is controlled by the position attribute. Positions are top, middle, and bottom.
-
The
scriptid
attribute is lowercase. -
The reference to a standard transaction form is uppercase and in the following format:
<transactionForm scriptid="scriptid" standard="STANDARDFORM"> ... </transactionForm>
The following is an example:
<transactionForm scriptid="custform_18_mstrwlf_612" standard="STANDARDONLINEORDERINVOICE"> ... </transactionForm>
You can also define the Custom Code tab and Actions tab in custom transaction form objects. For more information, see Custom Code Tab and Actions Tab in XML Definitions
For more information about custom transaction form format, see the reference documentation for transactionForm
in SuiteCloud Development Framework XML Reference.
Related Topics
- Transaction Forms as XML Definitions
- Supported Custom Transaction Form Objects
- Adding Custom Transaction Forms to Your SuiteCloud Project
- Custom Transaction Form Use Cases
- Custom Transaction Form Validation
- Limitations for Custom Transaction Forms
- Linking Custom Transaction Forms
- Custom Transaction Form Field Examples
- Custom Transaction Form Example