ThoughtSpot Best Practices - Alias or Role Playing Dimensions

What is the best way to model Alias or Role-Playing Dimensions in ThoughtSpot. For example I have an airport fact table with Origin and Destination. 

 

I also have a lookup table for Airport:  

Can I use 1 lookup table for airport or do I need to bring in the lookup table for airport twice (one to join fact to original_airport_id, one to join fact to destination_airport_id). 

Thanks!

3replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Steph, 
    You can use one table for airport and have multiple joins corresponding to origin/destination. When searching, the system will prompt the user to pick the desired path. If users are working against worksheets, the worksheet can have join paths resolved. Worksheets can have the same column brought in multiple times - each with a different join path.

    Like
  • Thanks - let me test it out. Ideally I don't want the user choosing paths (may be confusing). I'll proof out the worksheet approach. Thanks!

    Like
  • Quick update - I was able to set up the joins to one lookup table as you suggested. I then created a worksheet and picked the relationship for each element. From there I was able to pull the worksheet as a source and select available fields for an intuitive user experience. Thanks!

    Like 1
Like Follow
  • Status Answered
  • 2 yrs agoLast active
  • 3Replies
  • 585Views
  • 2 Following