Enhancement Request: Ability to include Lookup fields in Data Design Dataspaces

When creating a data designer table that includes lookup fields like company GSID, the look up configuration is not available. This prevents the ability to easily navigate to the lookup data in reporting and other places.

Not having this work as we would expect creates the need to manually put the look up data into the table and is not efficient.  We are constantly having to update the data designer object each time a new attribute is needed that would have been easily available with a lookup.  This also creates wasted storage as we have to include the data in the original table and in the data designer table.  

Awesome idea, @Brayden . I’ve long found the lack of Lookups to be a hinderance to be selecting Data Designer as part of a solution.

I think your Idea is very similar, or even identical to, this one. Take a look, and if similar, register your upvote there, where there’s already extended conversation and more upvotes to work with.

• Data Designer should dynamically honor lookups between tables New Idea
• 49 Votes