Two Valuelists: Default Values and Custom Values for Client

[ckai]

I hope my cryptic title hasn't confused everyone?!

Background: I have a value list called Unit. This has 3 values in it which correspond to the units of clients facilities (for example store room, front office etc). We select the unit for a client orders staff from us, so we know where they're going to be working. Obviously certain areas require different skills. They're pretty generic and these are fine for most clients. Some clients don't even need them.

We've come into a bit of a snag lately with a client have multiple locations. My idea was to use this Unit list as a way to stipulate what the location the shift is for.

My idea was to create another table called CustomUnits. This would have the fields ClientID, Unit Code, Full name of Unit. I'd then create a portal on the Client layout linked to this table so the user can enter in the custom units. I also planned on having an option box on the client layout which the user could choose to use the default Units or the clients own units. Of course, this may not be needed, i.e. if no values for the client are in the CustomUnits table then use the default list.

My question is: How do I get the custom units or default units to show in value list when appropriate? I was thinking of 2 separate value lists on top of each other, one which is used at the moment and the other is the Custom Units. Then if the "Use Custom Units" field is checked, the custom list would be visible/accessed.

I'm not sure of any other way (lack of skills obviously). It doesn't seem to be a conditional value list.

Thanks and let me have it :)

[eos]

You should do fine with a single, conditional value list:

Extend the CustomUnits table to be a Units table and add the default units. Give them a common, generic ID where the custom units have the ClientID. When the customer toggles his view preferences, set a global field to either the generic or the ClientID, and use this global field to control a relationship to the Units tables which fills the related/conditional value list.

I hope my cryptic explanation hasn't confused you yet?! (I had the same requirement from a model agency customer who, while assigning a model to a “mother agency”, wanted to toggle between this other agency's internal bookers and a list of freelancing bookers.)

[ckai]

Ah, very nice. I had to read it a couple of times to get it but it's a great idea. I'll give it a try and see what happens. Can't see anything going wrong though :laugh: