I have forms where the Total Amount field varies based on customer-selected options. Typically the user selects options in a descending order down the page to arrive at the Total Amount. This works as expected.
The form has problems when the user 'changes his mind' and re-selects from the same options that affect the Total Price. In this case, the Total Amount field is accumulated rather than overwritten. For example, the first time through the user might select options for 'Advanced Player and 'One Lesson Per Week.' Then, before purchasing, they might select the option for 'Intermediate Player' and 'Two Lessons Per Week,' which causes the Total Amount to change. Unfortunately the Total Amount field is accumulating the amount from the first choice with the second choice.
It does not seem to matter if I use the Fee Values field or the Fee Formula field to store the amount.
I can prevent the 'accumulation effect' by refreshing the page but I don't want to require a user to do this; the Payment Form should handle it.
In my recent journey to learn Payment Form I have gone through a number of iterations of creating forms and custom controls and then deleting/renaming, recreating forms and custom controls. At present I have approximately 270 Custom Fields being used across 10 or so forms. How does the Payment Form application handle database 'deletes?' Is it advisable to optimize or check the PF tables for integrity?
