Marketo Custom Object Overwrite | Community
Skip to main content
A
Anonymous
January 12, 2017
Question

Marketo Custom Object Overwrite

  • January 12, 2017
  • 3 replies
  • 1842 views

Hello,

We're starting to implement custom objects and I noticed that when I try to update my records custom object data, it creates a new entry. Like so:

Upload 1

Upload 2

The issue that I have with this is that when I enter in something like this where my preference is TRUE:

My lead record shows up.

And when I enter something like this where the value is FALSE

My record still shows up since both custom object data entries are contradictory.

Is this normal? Does anyone have a solution for this type of issue?

Thanks~

Message was edited by: Danny Tran

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

3 replies

SanfordWhiteman
SanfordWhiteman
Level 10
January 12, 2017

Pls move the question to Products​ ("Community" is for feedback about the Marketo Nation itself... confusing).

SanfordWhiteman
SanfordWhiteman
Level 10
January 12, 2017

Thanks for the move. Your top 2 images are broken (probably protected links). Can you update those?

A
Anonymous
January 12, 2017

Thanks for the corrections, Sanford. I've apparently lost all memory of how to post on these boards haha.

SanfordWhiteman
SanfordWhiteman
Level 10
January 13, 2017

I think the primary problem is your schema allows for contradictory -- or shall we say "unexpectedly multiplied" -- subscriptions, based on your screenshot.

If someone can subscribe to Automotive with en-us=true and at the same time subscribe to that same blog, Automotive, with en-us=false, that's going to cause filtering problems, even when you add additional constraints.

So I think you need to adjust the way you upsert custom object records.

A
Anonymous
January 13, 2017

Yeah I think you're right. I was trying to understand the thought process behind how our team set up this custom object and I am still having issues grasping their logic. They decided to enable Email, Subscribed To, and Type as dedupe fields, when I believe two of those three are fields that would have consistent changes made to them.

Thanks for your help on this topic.

Terms & ConditionsAccessibility statement

Loading footer...