I am having trouble with a trying to roll fields from multiple tables up into one "overview" table.

  • 0
  • 1
  • Question
  • Updated 2 years ago
  • Answered
I have an app with two local tables and two connected tables .The connected tables pull data from a separate QB app. 

I want to create a table that incorporates some fields from each of the other 4 tables in the app. Each table I'm working with has a Unique Identifier field. These values are unique in their table but match up to what record they correspond to in the other tables. 

The "overview" table I am trying to create has only has the Unique Identifier field populated. I'm able to get one table at a time to relate to the "overview" table, based on a relationship keying on the unique identifier field. But when I try to add a second table's relationship, there is not an option to choose my Unique Identifier field. Quickbase auto populated the reference field with a Related Record choice and the pull-down does not include the unique identifier. Help!

Should I be using Import instead of a relationship? Or what am I doing wrong?  Thank you!! 
Photo of Adam

Adam

  • 730 Points 500 badge 2x thumb

Posted 2 years ago

  • 0
  • 1
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 53,842 Points 50k badge 2x thumb
I'm not sure if I fully understand your question but I will try to answer.  

If you have  a table which already has a relationship built, and it is the child in that relationship, and that same table needs to be a child in Relationship #2, when you go to make the next relationship, that field that you already used in relationship #1 will not be available to use again.

So just make a field called [my field mirror] which a formula equal to the field that you need, and it will be available to use in a 2nd relationship.
Photo of Adam

Adam

  • 730 Points 500 badge 2x thumb
Thanks, that worked. Thanks very much for the help!
Photo of QuickBaseCoach App Dev./Training

QuickBaseCoach App Dev./Training, Champion

  • 53,842 Points 50k badge 2x thumb
It is non-intuitive that the field "gets used up" once used as a reference field on the right side of a relationship and that you need to do that cheat.
Photo of Matthew Neil

Matthew Neil

  • 31,478 Points 20k badge 2x thumb
I believe if you make that 'unique' field the 'key field' on the table, it can be used in any/all relationships made.