Hiding a form field should turn off prefill by default

Forum|Forum|9 years ago
November 11, 2016
5 replies
5375 views

When hiding a form field (setting it to "hidden" type), the prefill setting stays to "Enabled". If the user does not disable that setting, the field will not capture the values for the field on exiting, cookied, leads. The value from the database will prevail and the form will not work as intended.

And this happens!

So my recommendation is that, when a form field is set to hidden, the prefill setting should change to "Disabled" y default.

-Greg

Marketo

Grégoire_Miche2Author

Level 10

E.G: Re: Hidden Unsubscribe Field not changing Lead Info

Grégoire_Miche2Author

Level 10

added there: Just do it! Marketo so-called minor missing features

Dan_Stevens_

Level 10

So Marketo will not prefill a hidden field if the value exists within a lead record? Or is the issue here that if the desire is to modify that field (default value, URL parameter, etc.), Marketo will not populate it properly if it's pre-filling an existing value from the lead record instead?

Iryna_Zhuravel4

Level 6

it will pre-fill an existing value from the lead record, it can be very painful actually, as you might be losing a lot of data this way.

Grégoire_Miche2Author

Level 10

To complement the use case, I am thinking especially of boolean fields such as "Unsubscribe". Because, in this very case, forgetting to disable the prefill drives to breaching the CAN/SPAM and other similar regulations, which, IMHO, is worse than missing some attribution values

-Greg

SanfordWhiteman

Level 10

Only if you don't test it.

I think this is like the pURL oddities: you have to get the order of operations. Then there's nothing to screw up, because you build your solutions to the rules.

K

kh-lschutte

No text available

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded