Hallo,
Iam really new to all of the Timextender functionalities, so i have a small case/question for the Community:
I would like to join two tables and i dont know, if I first define the relation between the two tables or just drag the field into the othe table and create a lookup field then I will have the option to define a specific relation for this field.
Where are the benefits of creating a relation first ?
ty in advance
FEN
Best answer by fwagner
Hey FEN,
thanks for your question!
If you create the lookup without the relation existing between the tables, the join criteria are specific to the lookup only.
On the other hand if you create a relation between the tables, this relation is “universal”.
To be more specific, let’s say you add a second lookup field from the same table, and there is no relation you need to define again, which fields to join on.
And let’s say, at some point, the relation between the two tables changes (e.g. joining on different columns, or on another one (like tenant)), you’d need to adjust all lookup fields one-by-one, instead of just once adjusting the relation.
My general rule is to create relations between tables first and then use them in the lookups.
It will make your life easier down the line when your project grows.
HTH,
Frank
+4Hey FEN,
thanks for your question!
If you create the lookup without the relation existing between the tables, the join criteria are specific to the lookup only.
On the other hand if you create a relation between the tables, this relation is “universal”.
To be more specific, let’s say you add a second lookup field from the same table, and there is no relation you need to define again, which fields to join on.
And let’s say, at some point, the relation between the two tables changes (e.g. joining on different columns, or on another one (like tenant)), you’d need to adjust all lookup fields one-by-one, instead of just once adjusting the relation.
My general rule is to create relations between tables first and then use them in the lookups.
It will make your life easier down the line when your project grows.
HTH,
Frank
+5Hi
To add to what Frank shared we have two guides that we explain this in.
Is about how it works when you already have the relations before adding the lookup.
Is about lookup fields in general
Hey FEN,
thanks for your question!
If you create the lookup without the relation existing between the tables, the join criteria are specific to the lookup only.
On the other hand if you create a relation between the tables, this relation is “universal”.
To be more specific, let’s say you add a second lookup field from the same table, and there is no relation you need to define again, which fields to join on.
And let’s say, at some point, the relation between the two tables changes (e.g. joining on different columns, or on another one (like tenant)), you’d need to adjust all lookup fields one-by-one, instead of just once adjusting the relation.
My general rule is to create relations between tables first and then use them in the lookups.
It will make your life easier down the line when your project grows.
HTH,
Frank
Ty for your answer
Hi
To add to what Frank shared we have two guides that we explain this in.
Is about how it works when you already have the relations before adding the lookup.
Is about lookup fields in general
ty you. i will have a look
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
