Lookup Help

[Anonymous]

I am still having a hard time wrapping my head around how to correctly set up a Lookup in a dynamic block.  What I am intending to do is have a block that uses lookups to create a versatile sheet list set.

I have a "Sheet List" that varies depending on the city we design in.  In the block below I have the default options listed: (Cover Sheet, Site Plan, Mount Details, Electrical Diagram) with 2 other inputs which are a second and third layer of variables. #2 (Electrical Notes, Warning Labels, Electrical Notes & Warning Labels), #3 (Electrical Photos, Extra Electrical Photos).  I have the visibility states following this format 1 = the default sheets, the second number (0,1,2,3) = the #2 set of variables with the 3rd set of numbers (0,1,2) representing the electrical photos. *Note - 0 always equals "OFF".

I have the visibility states set up how they show look, I am stumped on how to create the lookups at this point.  I also am wondering if it is even possible to have the text shown in the right spots with lookups.  (That should be apparent when looking through the visibility states.)

Could you possible help provide an explanation of how I need to set this up to work?  I do appreciate the time!

[Libbya · Accepted solution]

There are various ways to approach this type of block.  You could potentially use a block properties table and attributes instead of visibility states.  Considering what you had already done and what you were asking, I made the following screencast.

[Anonymous]

Thank you!  This helped, it felt good to finally be able to build it.

The only question I have is what is the Parameter "Position" used for?  I don't quite understand the relation it has to this block.

[Libbya]

The Position1 X and Position1 Y properties are used as memory.  They store the selection input values for the individual selection lookups.  The double lookup then uses those relative positions to determine the row on the input table which in turn causes the change to the parameters on the output table (visibility parameter).

[Anonymous]

Thanks!  If I understand this correctly that would me I could not use those same 2 lookups for multiple sets.  I currently have 31 options that use those same 2 lookup selections.  I have attached a new .dwg that show all of the visibility states I need to incorporate.  I have tried and every time I use one of the lookups it sets all of the options to "CAD0..." options.  Do I need to create a position parameter for each set? (31)  I hope I am explaining this well enough...

It also looks like I could do a double lookup for each of the 31 sets that worked.  The only problem is I do not want to create 31 lookups if there is a better way.

Thanks for the help!

[Libbya · Accepted solution]

Add a third selection lookup in order to select CAD0, CAD1, etc...  Use only one double lookup.  The following screencast shows how to set it up but I only did a few in order to show the process.

Some things to note.  Do not draw your blocks far from the origin.  It's just bad practice and results in an errant base point parameter grip.  Also, in order for the block to work correctly, the Position parameters have to be located at a position that corresponds to values on the lookup table.  In the prior walkthrough, I turned all things visible and moved everything to the origin.  I then placed the Position1 point at 1,1.  I then set the visibility state that corresponded to 1,1 to the top of the visibility list.  If you do not do that, then you will end up with 'Custom' shown in the bottom of the selection lookups and the block will not switch properly until each lookup has been changed to a value that corresponds to a row on the double lookup input table.  

[Anonymous]

Thank you for all of your help through this.  I am starting to get a grasp on this.

I do have one more question, I have filled out everything and have this block set up how I would want it, however, the lookups are no longer working.  Yesterday when I had about half of them entered it worked fine.  Today I finished adding all of the values and now it is not working and I cannot find the issues. Looking at it are you able to let me know where I made my error(s)?

[Libbya]

It took a little while but I found the issue.  The output table of the double lookup (in this case the visibility table) MUST be 'allow reverse lookup'.  It was 'read only'.  When a table goes to 'read only' it is because you have more than one input value matching a lookup value.  It took a little while to locate, but you have 2 lookup values named 2f1 and that value corresponds to two different visibility states.  Because of that discrepancy, the double lookup could no longer switch the visibility state.  The second occurrence should be 2f31 instead.  Once that is fixed, the block seems to work.