Massive account DB in SFDC. Can it be filtered ? | Community
Skip to main content
Grégoire_Miche2
Grégoire_Miche2
New Participant
April 10, 2016
Solved

Massive account DB in SFDC. Can it be filtered ?

  • April 10, 2016
  • 3 replies
  • 2819 views

On a project, we are dealing with a massive account DB (>4Million) in SFDC. But, on the project, only a small part of it will be used (<1 million)

Does anyone know if the support can set a filter on the account object, as they would do on the contact and lead object, in order to limit sync durations and avoid flowing to Marketo literally millions of useless records ?

Thx in advance

-Greg

PS : we know we can restrict through sharing model and rules, but in this case, a simple filter would be much easier.

@Courtney Grimes​  @Josh Hill​, I know you probably have been there already, so, advise welcome

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 Steven_Vanderb3

We can set up a filter on most objects so feel free to contact support with the request to add a filter on the Account field.

3 replies

Steven_Vanderb3
Steven_Vanderb3Accepted solution
New Participant
April 11, 2016

We can set up a filter on most objects so feel free to contact support with the request to add a filter on the Account field.

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
April 11, 2016

Hi Steven,

Thx a lot

-Greg

Casey_Grimes2
Casey_Grimes2
New Participant
April 11, 2016

Hi Greg,

While I haven't dealt with this exact problem, I have handled a couple of similar scenarios that may help—one with Person Accounts with no corresponding Contact record (!?!?) and the other with high Account sync times. In the first case, I wound up just having to let the data sit in Marketo unassociated to any record even upon fixing it and as a result just wiped the DB and did a fresh sync with corrected records to fix the sync delay. Given that you're just starting out on this sync I'd probably just do the same.

In terms of account sync, you can in fact change the field you want the Account object sync to trigger on away from the last modified timedate, but it involves calling support to get that set up.

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
April 11, 2016

Hi Courtney,

Thx a lot

If you do not sync on last modified timedate, do you use another field (that you manage on your own)?

-Greg

Casey_Grimes2
Casey_Grimes2
New Participant
April 11, 2016

Hi Greg,

In short: yes, I just used another custom Account field + flows to handle the issue.

Thanks,

Josh_Hill13
Josh_Hill13
New Participant
April 10, 2016

Flattered you think I have a solution here. I probably should!

I'm not sure I Understand the exact issue though. why wouldn't a simple Sync = T/F flag work on the Marketo User Profile if you only want 1M/4M Account Records to go to Marketo?

if the Contact records cannot sync, then Marketo probably can't see the Account as well, right? You could flag both Contact and Account as Do Not Sync and that should work.

Am I missing something about this situation?

Do you actually want ALL Lead/Contact to sync, but not all Accounts? That sounds odd and a bit dangerous if a Contact syncs, but not its Account.

Grégoire_Miche2
Grégoire_Miche2Author
New Participant
April 10, 2016

Hi Josh,

In fact, by default, the Marketo user "sees" all the accounts and contacts in the DB. We have set a "sync with Marketo" filter on contacts.

But, Marketo syncs all the accounts (4M) even if there is no contacts to sync. We made a test on a sandbox, only 10 contacts had the "sync with Marketo" flag set to True, and yet the initial sync took 9 days (Yes! 9 days), because the whole 4M accounts have been sync'ed, prior to any contact being sync'ed.

So I am considering adding a "sync with Marketo" flag to the account also, and ask support to filter accounts on this field, so that only relevant accounts are synchronized, and I was wondering if this is a viable solution, if some has already done it.

-Greg

Terms & ConditionsAccessibility statement

Loading footer...