Skip to main content
darkknight
Expert ⭐️
April 21, 2020
New Idea

Data Designer should dynamically honor lookups between tables

  • April 21, 2020
  • 23 replies
  • 533 views

When I merge objects in SF with objects in MDA, and those objects in MDA have lookups to other tables, it would be great if the Data Designer set would honor those lookups natively, without me having to add all the fields I need into the dataset - especially since DD is creating MDA tables for you.

For example:  I have merged Opportunity Product with Company which contains a mapping of Account::Account ID to Company::SFDC Account ID.  

Instead of pulling in Company Name, ARR, etc. from the Company table, why can’t the DD table honor the lookup to the Company table via the SFDC ID natively?

 

23 replies

darkknight
Expert ⭐️
November 19, 2021

 @rakesh we need a solution as this is one of the most frustrating aspects of Gainsight.

Today I ran into a situation (that I’ve run into many times before, but I didn’t create this DD set, so I wasn’t aware) where I needed to map a Global Dashboard Filter to the CSM Manager GSID.  The field wasn’t showing up in a couple of instances and I discovered that the CSM Manager GSID in one of our DD sets was being rendered as a Text field.

 

This was because of the apparently limitation where you cannot traverse lookups more than 3 layers deep… so in the DD set, CSM Manager GSID was being sourced from Call to Action → Company → CSM → Manager (lookup) - which by the way IS an ID field in the source:

 

This is going to force me to add yet another dataset task to a DD set already made up of 13 tasks, just so I can pull in Manager GSIDs… this is just such a cumbersome feature to use.

Jeff Kirkpatrick
sacha
Contributor ⭐️⭐️⭐️⭐️⭐️
December 3, 2021

Adding another vote for this, would great increase the utility of DD for using in reports and dashboards!

darkknight
Expert ⭐️
April 8, 2022

Here’s that the Data Designer Templates isn’t the “solution” to this challenge, because all that does is potentially expedite building a DD set… it does nothing to solve that fact that DD is still creating duplicate copies of data fields that have to be regularly refreshed and have a high risk of being out of sync across DD sets.

Jeff Kirkpatrick