when creating a Customer Payment, what are the possible rules/validations/automations that can run in the background that, after selecting a customer, would reset the selection?

AI generated answer (using internal Slack threads):

Based on the provided Slack threads, when creating a Customer Payment, the following are possible rules/validations/automations that can run in the background that, after selecting a customer, would reset the selection: 1. Sourcing Timing: The issue of the customer selection resetting could be related to the timing of the sourcing. This could be resolved by creating a custom field on the Payment record, sourcing the customer into the custom field, and then setting a workflow that runs on the customer payment transaction and has a Set Field Value action (before user edit). This set field value will be set from the custom field you made. This allows the Payment to fully load but then before you start to edit it will add the customer and hopefully trigger the Apply lines. 2. Scripting and Workflow: Depending on the specific requirements, scripting or workflow could be used to handle situations where a Customer's payment Terms vary based on what they're buying. However, both would have to be done carefully to avoid resetting the customer selection. 3. Workflow on Record Load or Entry: To prevent a customer deposit form created off a sales order from prefilling the payment amount, a workflow could be created on before record load or on entry. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******