Passing Display-Only Values into FormLister Emails with formControls

FormLister usually feels straightforward when every value comes from a real input field. The donor case became interesting because one value, such as a displayed price, existed in the page markup but was not reaching the final email report the way the developer expected.

The missing piece was formControls. If a value needs to be tracked through FormLister processing and then referenced in a report or confirmation, it has to be treated as part of the controlled form state rather than as a purely visual placeholder.

Practical idea

&formControls=`price`

Once the value is part of the FormLister control set, it can be referenced reliably in the output template instead of disappearing between the visible form and the mail/report layer.

This is a good reminder that in FormLister, display logic and processing logic are not the same thing. If the backend needs the value later, the form pipeline needs to know about it explicitly.