Skip to main content
New Idea

Support more than one level in SFDC connector filtering

Related products:CS Data Management & Integrations
  • December 15, 2022
  • 3 replies
  • 37 views
KellyBebenek
elliotv
  • KellyBebenek
    KellyBebenek
  • elliotv
    elliotv

john.cowles

Currently, you can only navigate down one level in the filtering on Salesforce objects.  This is forcing us to not use the out of the box connector for syncing opportunity line and having to use a rule instead that does support more than one level.  This is a pain because now we have part of our integration of Salesforce data in the connector and part in a rule.  So we have to be dependent on getting the timing of these jobs right because there are dependencies that would normally be handled in a connector job chain.  

The reason we need this is that we need to filter the opportunity data we pull in to only active accounts which is defined using the “Account Type” field in SFDC.  For opportunity line data in Salesforce, you need to navigate first to the opportunity and then from there to the associated Account.  The connector will let us go from opportunity line to opportunity, but that is it.  So we can’t filter on Account Type like we need.  Given we do filter the opportunity data sync to only pull in active customer data, the opportunity line sync fails often on some data because there is not the associated opportunity in Gainsight.    

inagar
Forum|alt.badge.img+1
  • Gainsight Employee ⭐️
  • January 6, 2023

Hey @john.cowles , i do understand this feels exhausting to use connectors to bring in opportunityLine data and then using rules to filter out Accounts.

But this is the limitations from salesforce. Internally , Salesforce OpportunityLine item object does not lookup to Account Object of salesforce, due to which we cannot filter on account fields.


john.cowles
Forum|alt.badge.img+2

Thanks for the feedback.  I am not understanding how this could be a SFDC limitation when you can do it via Rules Engine and Data Designer.  I just tested both and you can filter down 2 levels.  So how could this be a SFDC limitation when 2 other data integration tools work and just not the connector?  

Here are the steps you can try to see this:

  1. Navigate to rules engine and add a new data set from “Production” (aka SFDC)
  2. Pick the Opportunity Product table which is the one the out of the box connector maps to the opportunity line item table
  3. Navigate through the available fields to the opportunity id and expand this section
  4. Navigate in the opportunity to the Account related table and expand it
  5. Navigate to Account Type

See this screenshot show how it was selected.  

 


jordan_cook
Forum|alt.badge.img+2
  • Contributor ⭐️⭐️⭐️⭐️
  • July 18, 2023

I agree with @john.cowles . This seems like a parity issue with the Rules Engine. We are able to filter more than one level deep within a rule, but are not able to do so within a connector job.

 

Because of this, we end up pulling in far more records than needed. I honestly feel like this just hurts Gainsight servers/infrastructure more than it hurts me. The more selective I can be, the more efficiently I can write rules that reduce the load on your servers.



Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings