Multiple Salesforce Custom Object records causing confusion!

[Anonymous]

Ha - I appreciate the help, I really do - but it won't work - we have at least 5 other use cases using date fields on these custom objects that have been worked out by our Customer Success team - I just need to figure out a way in Marketo to execute them.

Also, adding fields from custom objects to the main objects is also kinda like saying that the Marketo Custom Object features don't work very well...imho

🙂

[Grégoire_Miche2]

Hi Michael,

adding fields from custom objects to the main objects is also kinda like saying that the Marketo Custom Object features don't work very well

I agree with you but at some point, it's about making it work

but it won't work - we have at least 5 other use cases using date fields on these custom objects

The solution above is having a field on the Main contact object, not the custom object.

Has the CSM been able to make the other use cas work? Any learning on these about what works and what does not ?

-Greg

[Anonymous]

Hi again,

the CSM is only working with the data in Salesforce at the moment, making sure they are getting the Contacts that they think they want to communicate with based on the data within the User Custom Object - they then ask me to make it work from the Marketo side of things...

I understand the points made about putting mapped fields onto the Contact object itself based on data coming from the User record - but we have different use cases using different date fields etc, so my last resort will be to go back and ask them to map all of these fields onto the Contact record.

My main query here really is this: -

if I can pull 17 Contact records in a Salesforce report who last logged in on the 8th March 2017 - using a custom report type where Contacts are associated to the User object

AND

if I can pull those same 17 Persons in a Marketo smart list using the 'has User' filter with the constraint of last logged in date being the 8th March 2017

then WHY does the same logic not work with last log in date being in past before 365 days and in past 366 days - which equates to the 8th March 2017...doesn't this all point to the fact that the filters don't work as expected on Custom Objects? I'm pretty sure I get all 17 of the original people included here, but for some reason I also get a whole bunch of others who don't meet the criteria as far as I can tell...

[Grégoire_Miche2]

I just emailed you, I'll give a direct look, just in case I see something...

-Greg

[SanfordWhiteman]

(I'm talking about a field on the CO.)

[Grégoire_Miche2]

That one would work too, indeed. A formula field would be enough, provided that all the "user" CO are updated in SFDC to initialize the database after the field creation.

-Greg

[Josh_Hill13]

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.

[Grégoire_Miche2 · Accepted solution]

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

[Anonymous]

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!