Data Designer should dynamically honor lookups between tables

@keith_mattes  @heather_hansen @travis_floyd Here’s the response I got from GS product.  I don’t quite buy it - but it is what it is:

“DD is architected and built to create flat sets that are very easy to understand and very fast to report on. It's not possible to have lookups again after the final dataset. It wouldn't work both at a data store level or at a reporting level. 

Doing that would require either a complete re-building DD from grounds up (very hard given the adoption) or a lot of effort to have a very limited ability to only have a lookup to Company with eventual consistency sync. The latter can cause a lot more confusion since it might take a lot of time to sync Company values to the new data store. I'd call this using a screwdriver as a hammer - we might be able to do it, we would need a lot of time to inefficiently solve this. It's not recommended and would distract us from the core mission of lowering the barrier to work with data - making data prep even easier and consistent across Gainsight.”

I can understand the potential complexity, but allowing JOINS in the resulting dataset AFTER a merge is created would be INCREDIBLY powerful.. and save Admins a TON of time … this would essentially be creating a Dynamic Data Designer Dataset (DDDD) and I’m trademarking that… 

Definitely +1 for us as well! @keith_mattes yass DDDD would be epic 

Due to so many requests on this one, we will exolore technical viability on this. Do note that its not very straight forward and its very easy to introduce suboptimal solutions. Hence we might take some time on this one. 

Very happy to see this posted this morning!!!  While it may “disrupt” the traditional hub-spoke data model used in the MDA (all roads lead to the Company Object), the power behind this is immense.  And yes, also a bit “tangly” in the backend… should Gainsight ever want to review/consult with the Global Admin group, we can raise this as a topic and drive some feedback and ideas if you wish to partner. 

Allow data designer MDA to add lookup configuration with respective GSIDs to Company, Relationship, Success Plans and CTA objects. As we know DD are limited to 50 fields MDA, we could not build a solution having company or relationship MDAs all data. If Data designer MDA fields could allow edit to lookup additions will bring in more scalability of using it more than rules. 

+100

Just adding a +1 to this!

This would be incredibly helpful to keep DD more simple and more powerful reporting!

YES YES YESSSSS A THOUSAND TIMES YESSSSSS

+1000 running into this issue now. Would love not to add every field into my current DD or even have to create a new DD with ALL the additional fields that already exist in a related table.