Can you block fields from updating based on some kind of user record segment? | Community
Skip to main content
J
Jeff_Bedford
New Participant
January 14, 2019
Solved

Can you block fields from updating based on some kind of user record segment?

  • January 14, 2019
  • 1 reply
  • 4167 views

Hey All-

Here is what I think may be a unique problem. We have a B2B2C model. All of our B2B records were loaded in from SFDC and overall, the sync has been great. It's allowed us to do a ton of good work.

But, we also have a web services API that loads in our B2C records. We have done a bunch of work to isolate the fields being used by our B2B records and B2C records - to prevent overlap. Unfortunately, there remain a few fundamental fields like name and email address. What we are finding, is that at times, our web services API is loading in/updating B2C records that have an email address matching one of our B2B records - therefore overwriting some key fields in both Marketo and eventually SFDC. Obviously, this has big problem potential.

Our gut feeling, is that if we could find a (ideally dev-free) way to tell Marketo we don't want that API to update records that have a SFDC ID - this would squash the problem all together.

Anyone have any good ideas?

    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 SanfordWhiteman

    Can't be done the exact way you describe.

    However, you can make these fields not updatable (for all leads) via API by blocking field updates in Admin. Then create proxy fields that are updatable. When the proxies are updated use a filtered SC + Change Data Value to update the real fields.

    1 reply

    SanfordWhiteman
    SanfordWhitemanAccepted solution
    New Participant
    January 14, 2019

    Can't be done the exact way you describe.

    However, you can make these fields not updatable (for all leads) via API by blocking field updates in Admin. Then create proxy fields that are updatable. When the proxies are updated use a filtered SC + Change Data Value to update the real fields.

      J
      Jeff_BedfordAuthor
      New Participant
      January 14, 2019

      Thanks for the quick reply man. One question. If we block the fields from being updated via API - would the API still load them in if it was a net new record? that would be ideal if we could allow the API to create new records, but never edit fields on existing ones. We wouldn't even need to use proxy fields at that point, I don't think.

      SanfordWhiteman
      SanfordWhiteman
      New Participant
      January 14, 2019

      Yes, can set initially but not update.

        Terms & ConditionsAccessibility statement

        Loading footer...