Deleting Custom Transaction Types with a Bundle
Custom transaction types can be removed as part of a bundle removal or a bundle update.
Deleting custom transaction types applies only to bundle operations. If a custom transaction type was created manually in the UI and a transaction instance exists, you can't delete the transaction type.
When a bundle operation is used to delete a transaction type, the system takes the following actions with any existing instances of that transaction type:
-
The transactions are migrated to a new transaction type called Deprecated Custom Transaction.
-
The transactions are locked to editing, although they can still be voided.
-
If the transactions are in open periods, they can be deleted.
-
Body fields are added to the transaction showing:
-
The name of the custom transaction type that was deleted.
-
The status of the transaction at the time it was deleted.
-
-
Associated printing templates are deleted.
-
Custom fields are discarded unless they're related to a custom segment that has GL impact.
To see a list of transactions that were instances of deleted custom transaction types, use the Transaction search type. Set the Type field to Deprecated Transaction Type.