What can you do with a LookUp Table?

[aclarke]

Hi all.

I am interested to know what you can use a Lookup Table for above and beyond MEP fittings?

I watched a demo today on lookup tables and in another post I just posed someone mentioned I should  use Lookup tables and a lot can be done with them.  I am short on imagination on how to use them out side of MEP fittings... 

So, What and How do you use Look Up Tables, ideas?

Thanks

[RPTHOMAS108]

They work similar to vlookup function in Excel (except only valid for looking up numerical values) i.e. in a table there is a column containing keys to the left and based on the value of key you return a value from the cell at the intersection of the named header column and the row the key is on.

Mostly they are used where instance parameter variations need to drive other instance parameters. Meaning there is a set of possible values for an instance parameter and the one selected is based on the value of another instance parameter. Basically where it is impractical to create all the type variations that you would otherwise need to if using type parameters and type catalogues for the same.

The other advantage is the csv input may come directly from product information tables so it can be quickly formatted and imported. They are mostly used in MEP as you say, not seen them used much outside of that. I don't think there is any real need there.

Lookup Tables | Revit | Autodesk Knowledge Network

I also noted this a while back:

Solved: Re: Creating Window Library with all combinations - Autodesk Community - Revit Products

Perhaps there are a set of parameters whose combined permutations could vary beyond a practical set list of types i.e. you don't know what someone is going to request but you can allow for all permutations and so number them in a logical way to put a simple number id to the exact request.

[RDAOU]

@aclarke 

Here is a simple example - You model a Table with a single generic type only (Variations are too many to create a type for each)

• Length, Width and Color or Material are Instance parameters

You place in the model 10 instances in Black, 20 instances Blue, 30 instances in Green ...etc

• Condition: Dimensions of the tables (instance parameters) are driven by the color
• Application: based on the color you define the lookup table will fetch the dimensions from the csv file

Thinking more out of the box.

You want to link your store inventory to the model and report what you have in stock/storage.

1. Add another instance parameter "Qty in Stock" and its corresponding field in the csv
2. Get the guys at the stores (who has no clue what Revit is) to update the quantities in the csv/excel based on color
3. Use the new csv to update the lookup table in the model 

Having to do the above for 1 family, one might say, "Meh!!! keep it simple no need for all that" ... having to do it for 10s of families, the above will save you days of tedious work.

With a little bit of Dynamo skills, you can automate all that to update a 100 families in 1 click. (what this guy was trying to do in This POST Here >>> Size Lookup Tables Local Storage