Blocking Field Updates

Forum|Forum|8 years ago
September 22, 2017
3 replies
4751 views

In field management, if I use the "Block Field Updates" functionality, does that block those sources from entering data in blank fields or does it only block those sources from overwriting existing values?

Thanks for the help!

Marketo

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

SydneyMulligan

Level 7

Both!

SanfordWhiteman

Level 10

Actually no... it's intended to block updates to existing non-empty values, but an empty string can be updated. This has always been an annoyance and I wish it worked the other way.

SydneyMulligan

Level 7

Oh really? Wow I always thought it worked the other way too. There should be better documentation about this. It's not worded very clearly in the product doc.

SanfordWhiteman

Level 10

Yeah, it's the reason I fill fields with "[not provided]" or "[none]" by default.

Monica_Koran

Level 3

Hi Sanford -

Quick question, when you say you add in [not provided] as a default value do you add that in the autofill listed here? or do you have an operational campaign that does this on the back end. Asking because I thought if you add a default value here as listed below then all your fields will have [not provided]. Again the documentation isn't really clear here. Thanks for your thoughts!

A

Anonymous

Thanks everyone - so to summarize, it blocks updates to field values but will allow empty fields to be populated by any blocked source.

This actually works the way I wanted it to; our lead source data is a mess so I am working to ensure all programs populate this cleanly and was checking to ensure I wasn't errantly overwriting values (or if I needed to put conditions on the smart campaign flow to only populate when lead source is empty).

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded