Unknown Default Values in NWF

[rupertvz]

Hi Guys,

I have a form completing default field values upon insert, and I don't know where these are coming from.

What determines a field's default "cookie" value?
How can I prevent default field values being populated from cookies in a NWF?

[peterH]

Maybe from your dictionary?

Peter

[Bruce]

Hi Rupert,

Fields are not populated from cookies. So probably best not to use that word in this context as it will be confusing.

Forms have a "Priming" tab. On insert fields are primed based on what is here.
Table-Fields are cleared on insert (and then primed from the priming tab).
Local-fields on the form are not cleared. If you want to clear them do so on the Priming tab.

cheers
Bruce

[rupertvz]

Thank you Bruce,

These are table fields.
It is an e-mail address field and cellular number field which are populated by unknown values.

There is no priming for these fields under the "Priming" tab.
The initial values for these fields in the dictionary are also blank.

Not sure where these values are coming from, it seems to be browser (Chrome) related.
Testing the same in IE gives blank fields.

[peterH]

Ahh, now I think I know what's going on.

The fields are not being primed per se. What happens is that Crome tries to be clever as soon as it sees a field that may be an address, a phone number or a website and suggest some values based on prior data being entered. I've seen that myself, and only if the user hits Enter the fields are actually filled with the suggested values.

I haven't investigated further, but there may be a way to turn this "feature" off, who knows.

Peter