Behavior of Classification Fields Following Edits to a Custom Transaction Type
This topic describes how edits to classification field settings affect both existing and new instances of a custom transaction type. For an introduction to classification fields, see Custom Transaction Type Classification Fields.
When you edit an existing custom transaction type, you can change the settings related to class, department, and location. Any changes you make affect existing instances of the transaction type, as well as new ones. If you make changes, note the following:
-
If you move a field from the Lines sublist to the header, the new header field is populated only if all of the fields on the transaction instance’s Lines sublist shared the same value. Otherwise, the field’s value isn't defined. If you change the location back to Lines, the former values are restored.
-
If you choose to make a field mandatory that was not previously required, existing transaction instances may not have the required value. However, a user editing one of these instances is required to enter a value before being permitted to save changes.