About $0.02's worth of observations...

May 13, 2008 at 4:03 PM
Nice!  Funny enough, we just did a very similar implementation on a project back in January, and then scrapped it in favor of MULTIPLE config lists, essentially one for each Category.  The reason we did this is that we realized we needed to use the values in lookup lists, and we didn't want to go to the length of creating a filtered lookup column field.

That said - if a generic FilteredLookupColumn field type did exist, say using a CAML query string for the filter, then this would be a great generic utility.
Coordinator
May 13, 2008 at 9:15 PM
Interesting, thanks for the comment..

I'm currently using separate lists for lookup information, but the idea of making the utility read across multiple config lists is an interesting one..