The problem is if they check and uncheck the checkbox, you will not know if the checkbox state at form submission was the original untouched state, or if they deliberately changed it.
If you continue to use a checkbox, and If applicable laws require you to not reflect earlier consent -- even when the consent was expressly given in the past and you can show them the timestamp -- then there's no solution to this problem. You'll never be able to distinguish "do not change stored value" from "change stored value to 'no'" with just a checkbox.
You can switch to radio buttons Subscribe/Unsubcribe/Do Not Change instead.
Thanks for the response. That was exactly what I was thinking regarding the smart campaign approach with the checkbox.
Okay, I can add the radio buttons as an option for us to consider. One follow up question I have for you regarding the select boxes. When we create a select box, we have the following options with the displayed versus stored values:
- Select... |
- Yes | TRUE
- No | FALSE
Just so I understand this properly, if the customer leaves the select field set to "Select..." which is matched to a NULL stored value, this should not overwrite an existing value of "TRUE" with "NULL" correct?
1 of 1 people found this helpful
Empty stored value won't overwrite.
The actual string "NULL" will overwrite.
See here, perhaps, for more: http://blog.teknkl.com/clearing-lead-fields-when-no-value-submitted/
Fantastic, thanks as always for the help Sanford!