Blocking field updates depending on record-based criteria | Community
Skip to main content
A
Anonymous
January 16, 2013
Solved

Blocking field updates depending on record-based criteria

  • January 16, 2013
  • 12 replies
  • 3906 views

Hi there,

Is it possible to block updates to a field on some occassions and not others? And I don't mean depending on which source it's come from (i.e. list vs form fill-out), but depending on record-based criteria (i.e is a user vs is not a user).

Example:
I have a field that for some people - let's say, record type A - I want to update and NOT block.
For record type B, I use the exact same field but for them I DO want to block any updates from Marketo AND I want to block that field from even being populated by Marketo when it's empty. 

Is this possible via Marketo or only via Salesforce? If the latter, does anyone know how to implement? Can you create a new profile for the Marketo user in Salesforce that includes all the same permissions except the ability to edit field X on record type B (but still allow it to edit field X on record type A)?

It sounds like the easiest solution would be to create a different unique field for each record type, but we're so entrenched with using it across campaigns and with syncs with our data warehouse that this would actually be extremely cumbersome for us. We need a quick, solid fix.

Any help appreciated!

Cheers, Tara

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by
One last thought - you could import the data into a new Marketo only field.  Then create a triggered smart campaign that would update the value in the current synched field of only those leads with a field value of "Record Type A" as follows:
  • Smart List - Data Value Changes trigger with "Attribute: [new Marketo only field]" and a "Record Type: is Record Type A" field filter
  • Flow - Change Data Value flow action with "Attribute: [synched field name]" and "New Value {{lead.[new Marketo only field]}}"
  • Schedule - Each lead can run through the flow every time

12 replies

Show previous replies
A
Anonymous
January 24, 2013
YAY!  Thanks!
A
Anonymous
February 4, 2013
Hi Elliott,

I have just realised that it seems to be processing when the name already exists in Marketo but not when the name in the list I upload is NEW. I thought Marketo viewed the data as “changed” even when the lead has just been created, but it doesn’t seem to. Can you think of a way to incorporate this into the one campaign so that it caters for both new and existing names who have the data value "updated"?
 
Or, do you think best to create a sister campaign that uses the same flow and schedule but instead the smart list looks for NEW lead created AND data value [new Marketo only field] not empty AND record type is record type A.

Cheers, Tara
Terms & ConditionsAccessibility statement

Loading footer...