Relationship
I am trying to connect two tables, both having the same Primary key fields. However, they are not connecting and returning look-up field data. Both of my Primary key fields are Compostie type - is t...
Forum Discussion
It isn't clear by your post whether you have related the tables together or not. It is also not clear what related data you wish to show here. That will determine the type of relationship you need to create. What do you mean by both fields are "Compostie" type fields?
We just need more information on the tables and what you are wanting to do.
https://help.quickbase.com/user-assistance/creating_a_relationship.html-------------------------------------------
Original Message:
Sent: 02-09-2021 13:02
From: Alycn Bjergo-Justen
Subject: Relationship
I am trying to connect two tables, both having the same Primary key fields. However, they are not connecting and returning look-up field data. Both of my Primary key fields are Compostie type - is that why? If so, how can I connect the two tables another way?
------------------------------
Alycn Bjergo-Justen
------------------------------
We just need more information on the tables and what you are wanting to do.
https://help.quickbase.com/user-assistance/creating_a_relationship.html-------------------------------------------
Original Message:
Sent: 02-09-2021 13:02
From: Alycn Bjergo-Justen
Subject: Relationship
I am trying to connect two tables, both having the same Primary key fields. However, they are not connecting and returning look-up field data. Both of my Primary key fields are Compostie type - is that why? If so, how can I connect the two tables another way?
------------------------------
Alycn Bjergo-Justen
------------------------------
No the relationship is returning no data in the fields.
Table1 Primary key is composite field of CustomerID and TrackingID.
Table2 Primary key is composite field of CustomerID and TrackingID.
I want to bring in a field from Table2 called Order Number into Table1. However in my relationship, no data returns.
Thank you,
Alycn Bjergo-Justen
Director of Business Applications & Support
P 888.390.5320
D 651.209.3842
SOLUTIONS MADE SIMPLE.
- For one thing you cannot have a formula as a primary key. That is not possible any longer. There used to be a bug that allowed it to be set by API but I believe they fixed that. You can have a MERGE field be a composite field as you call it. That can be used to import data. So it should not be possible at all to do what you have described so far. I didn't understand that you meant you made a formula field when you said composite.
You will need to figure out how your data relates in another way. You can do this in many ways depending on your data. From your forum signature it looks like you are creating something for a shipping company. You could relate everything back to a Contact and have them be the key for everything. That way the contact owns the orders and you can relate things in that way. The contact could be a person or a company. If it is a company you might consider going with both a Company and a Contact table in case you need multiple contacts. - What is the business logic in having the Primary Key of 2 tables comprised of the same data? To me, this would mean that the two tables hold pieces of the same thing, rather than an true Parent/Child relationship. Can you provide a bit more context as to what these two tables represent? Also, if you could provide a screenshot of your relationship between the two tables, that may help answer some other lingering questions.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quickbase Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
