Looking for some advice on Lookups. I'm desi...

(Andrew Eills) #1

Looking for some advice on Lookups.

I’m designing an app that will have about six lookups.

I want to put these in tables, rather than enums, so they can be updated.

I’m thinking of putting them all in one table, having a ‘type’ column, as well as the lookup value column (they will all be Text type), so that I can use a Valid_If to filter by lookup type to get the relevant lookup values in the relevant parts of the app.

Is this normal/efficient?

I just don’t want to have six lookup tables.


(Aleksi Alkio) #2

Are they for ref fields or just simple Valid_Ifs?

(Andrew Eills) #3

Just simple Valid_Ifs.

(Aleksi Alkio) #4

You can read all separate columns from the same table with a formula like SELECT(Variables[ColumnB],TRUE,TRUE) for your Valid_Ifs.

(Andrew Eills) #5


I just wondered whether it was common/best practice to put values for different lookups in the same column of one table, or whether there was another, ore effective way of doing it.

(Andrew Eills) #6

Oh, I think you may be saying that it’s best to have each set of dropdown values in a different column of the same table, and just pull them into the relevant dropdown by selecting all values in the relevant column (even though the table rows are going to have loads of empty cells, because the number of dropdown values will vary across columns)?

(Aleksi Alkio) #7

Add one key column (Column A) to your table and you don’t need to think about empty cells.

(Andrew Eills) #8

OK, got it. Thx

(Aleksi Alkio) #9

You’re welcome