Multiple Salesforce Custom Object records causing confusion! | Community
Skip to main content
A
Anonymous
March 8, 2018
Solved

Multiple Salesforce Custom Object records causing confusion!

  • March 8, 2018
  • 3 replies
  • 4688 views

Hi guys,

I need a smart list to select people based on their latest login date (which is stored in a 'User' custom object which sits off the Contact object in Salesforce). I'm using the 'Has User' filter and 'in past before' and 'in past' to get to a group of people whose login date was 180 days ago, and some of the people records I get returned are good - i.e. they have the correct Login date I would expect, and some don't, and some have no date at all. So we added another 'Has Platform User' filter to try and avoid those with no date at all...but it's not working. Is there some issue with this if the Contact has multiple User records? I need to find a way to filter down to a specific User record, and from there filter on the dates...but it doesn't do what I would expect it to.

And this got me thinking about how you are selecting audiences based on Opportunity data - because a Contact can be associated to multiple Opportunities - so again let's say I want to pick people who have a certain type of Opportunity record (we differentiate renewal and standard opportunities in Salesforce), within a specific date range - it's possible that a Contact might have multiple opportunities, and even multiple renewal opportunities, so how do you deal with the filtering out of older/other Opportunities in favour of specific ones, or how do you set up your filters so that only the ONE opportunity you want to reference is being used - and you're not just pulling people who meet the criteria on 3 or 4 of their Opportunity records? does that even make sense! :-)

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 Grégoire_Miche2

Hi Michael,

Documenting the solution here in case someone searches the community.

when looking for any person that have 1 linked User CO that have a login date 1 year ago can be resolved with 3 smart list:

  1. SL1: has User, constraint: Login date in past 366 days
  2. SL2: has User, constraint: Login date in past 365 days
  3. Target list : member of Smart list in SL1 and member of smart list not in SL2

-Greg

3 replies

Grégoire_Miche2
Grégoire_Miche2Accepted solution
New Participant
March 12, 2018

Hi Michael,

Documenting the solution here in case someone searches the community.

when looking for any person that have 1 linked User CO that have a login date 1 year ago can be resolved with 3 smart list:

  1. SL1: has User, constraint: Login date in past 366 days
  2. SL2: has User, constraint: Login date in past 365 days
  3. Target list : member of Smart list in SL1 and member of smart list not in SL2

-Greg

A
Anonymous
March 13, 2018

Thanks Greg - when I stopped jumping for joy round the office I was going to ask if you wanted to publish the solution - this worked for me, and now I know how to approach the other requirements I have where I need to use dates in COs...thank you!

Josh_Hill13
Josh_Hill13
New Participant
March 8, 2018

This is definitely a concern with Marketo.

For SFDCCustom Objects, I'd suggest going through the setup carefully because the data should be there.

One way we handle targeting specific Opps and Contacts is to export the SFDC IDs and re-match them with a filter or hope that the email addresses at least match roughly the right records. Unfortunately, the only real matching tool would be to use middleware like talend to match SFDC IDs properly and Add to List.

Jep_Castelein2
Jep_Castelein2
New Participant
March 8, 2018

For both Custom Objects and Opportunities you need to put all your criteria in one Smart List filter. As soon as you put 2 filters on the page, they may match different Custom Object records, rather than applying all constraints on a single Custom Object record.

A
Anonymous
March 9, 2018

I see what you're saying - but it's not possible - the Marketo doc says that when you're using things like 'in past before' in your date filter then you ARE going to pull people back who have NULL in the date field you're using. The suggestion to get round this is apply the 'is not empty' filter on the same field and as you can't reference the same field more than once in a single smart list filter there is no option to but to drag in another one and try to do it from there...

SanfordWhiteman
SanfordWhiteman
New Participant
March 9, 2018

Add a new field with Boolean type, like hasLoggedIn, and additionally constrain on that.

Terms & ConditionsAccessibility statement

Loading footer...