Conditionally block field update with block / unblock flow steps

[Grégoire_Miche2]

Today, we can block field updates based on source. But we would need to be able to do the same thing only in certain records.

Originally, this idea was about having 2 choices for each field and each source:

• Block always (currently available)
• Block if member of smart list, to be specified by the admin.

But Sanford Whiteman​ made good point re. performance issues and proposed a much better solution (see below): having a "Block field update" and "Unblock field update" flow steps that would do the job for each lead. The flow steps would have 2 parameters :

• Field name (with the capacity to select multiple fields)
• Source (with the capacity to select multiple sources)

Use case:

• Make sure that certain contacts from the CRM would not have their key information updated by a Marketo form, a field update not a Change Data Value
• Make sure that some records that are sync'ed by a third party software through API could have their sync UID blocked from any update, only when they are of a certain type...

-Greg

[SanfordWhiteman]

I'd worry a lot about resource utilization from checking SL membership at runtime.

Counter-proposal: taking a cue from JavaScript property descriptors (my favorite language feature), allow fields to be locked and unlocked using flow steps, constrained by source(s). This way each value's access control metadata can be stored directly on the lead.

[Grégoire_Miche2]

Hi Sanford,

Good point. A Static list membership or a segmentation could also be a good starting point.

I like a lot the idea of locking / unlocking a field using flow step. I think it's better, so I have reworded the idea.

taking a cue from JavaScript property descriptors

What does that mean for a mere mortal ?

-Greg