Custom Transaction Type Classification Fields
Classification fields, including the Mandatory boxes, aren't available for the sales and purchase custom transaction types. For sales and purchase transaction types, class, department, and location and determined automatically based on the features and preferences enabled in your account. You can use form customization to configure whether classification fields are available for sales and purchase custom transactions.
Custom classification fields in custom transaction types provide flexibility for tracking class, department, and location values. Specific behaviors and settings, such as global preference impacts, numbering implications, and how changes affect existing records, are described in the following topics:
-
Classification Fields in Numbering for a Custom Transaction Type
-
Behavior of Classification Fields Following Edits to a Custom Transaction Type
For each transaction type, you can decide whether instances of the type include fields for class, department, and location.
Your choices for each of these fields are as follows:
-
None – (Default choice) The field isn't used.
-
Header – The field is displayed on the transaction’s body.
-
Lines – The field is a column in the transaction’s Lines sublist.
For each field, you can also check a Mandatory box. If you check this box, users entering transaction instances are required to enter a value for the field.
Your choices about these fields are all reflected on the standard form for the transaction type. Your choices are also reflected in the default configuration of any custom forms you create, although you can make changes to the custom forms. For example, on a custom form, you can hide any of the classification fields, even if the transaction type was configured to make the field visible and required. In this manner, you can bypass the transaction type’s settings.
Your custom transaction type can be associated with a plug-in implementation. If it is, consider the logic of the plug-in implementation before setting these fields. Specifically, the plug-in implementation may set line values for class, department, or location. If it does, you must set the Class, Department, or Location list to Lines. If you don't, the values provided by the plug-in aren't used.
You can set values for the classification fields both when you create a custom transaction type and when you edit one. For details, see Creating a Custom Transaction Type and Editing a Custom Transaction Type.
Related Topics
- Impact of Global Preferences on a Custom Transaction Type
- Classification Fields in Numbering for a Custom Transaction Type
- Behavior of Classification Fields Following Edits to a Custom Transaction Type
- Creating and Editing Custom Transaction Types
- Custom Transaction Styles Overview
- Creating a Custom Transaction Type
- Editing a Custom Transaction Type
- Locked Custom Transaction Types
- Custom Fields in Custom Transaction Types
- Numbering for a Custom Transaction Type
- Account Field Setup for Custom Transaction Types
- Statuses for a Custom Transaction Type
- Creating Links for a Custom Transaction Type
- Adding Custom Forms for a Custom Transaction Type
- Permissions for Custom Transaction Instances
- Adding Translations for a Custom Transaction Type