While trying to implement automation to update transaction line Class fields based on some business rules, I found that if I switched forms to a custom form that had Class un-checked (not visible) and saved the transaction, the underlying sublist Class fields were not available in my beforeSubmit event.
Action:
- Load the transaction for edit and see that Class is selected on various lines.
- Switch forms to a form that does not have Class as a visible field.
- Save the transaction.
Expected: I expected that beforeSubmit would still have access to Class so I could set values based on our business logic. Scripts have access to all the underlying data, right?
Reality: The Class field is missing from the item sublist and is apparently submitted as null—and the Class is wiped from all the sublist lines!
Is the connection between form and the underlying data that strict? I tried moving my code into afterSubmit, and even after a record.load() the item sublist didn't have Class—probably due to the form selected at save?
Am I missing a best practice for modifying form layouts without losing data?