Clarity

We currently have a static list lookup on the project object (Category, believe its part of PMO Accelerator). We would like to add a new lookup that presents a set of values only if a specific value is selected in the Category lookup, otherwise it would be null. Ideally, the new lookup would also be required if the first value is selected.

I thought maybe Lookup Mappings would work as I found a version of the Category lookup that is based on the Mapping list tied to the project Type, which seems very similar to what we would like, but I can't figure out how to create new mappings rather than just adding to the Type/Category ones.

You could do this with a parameterised lookup (where the parameter is the project id and then NSQL in the lookup uses that to read the relevant options to present to the user) - but this would only work if you have previously saved the first lookup value.

I had considered that but ruled it out for the exact reason you mentioned, the requirement is to show the values in lookup #2 as soon as the option is picked in lookup #1

So you can do something like that with "lookups within lookups" ; you don't have 2 lookups on the main object, you have one, but that one lookup contains itself another lookup as a filter field. This is somewhat similar to a static-dependant-lookup, but with the advantage that you can code (NSQL) the logic rather than it being static.

(not sure I've explained what I mean by "lookup within lookup" very well ; I am trying to say what happens when you set up a "Lookup Filter" within a lookup)

I take it then I'd have to create a new object to store the values for lookup #2 right for it to query the DB rather than just have a list? Never actually had to make a dynamic lookup before so this is still new to me.

No, no new "objects" or anything like that needed... the second lookup (in my badly-worded explanation) would be dynamic (i.e. NSQL based), the first lookup could be dynamic or static.

(so dynamic/NSQL based lookups can draw their data from (literally) anywhere; this can be selected from an object if thats what you need, but is more likely to be selected from existing data in your database (of course I am making vague-guesses about your actual requirements/functionality here))

Hi Dave,

I have a similar requirement as below:

Need to configure two fields on the Clarity General overview page.

Both will be marked required.

1. Attribute #1

Values Pick one – Yes / No / Not yet known

2. Secondary Product Line

Values : A/B/C

Ideally, field #2 would only appear if answer to #1 is yes.

Can you Please suggest?

Check this -

Create Dependency Levels for Static Dependent List Lookups

https://communities.ca.com/message/100670485#100670485

NJ

And this -

Dependant lookup

https://communities.ca.com/message/2281021#2281021

NJ

Hi, I have clarity 7.5.3 which I suppose from the above threads suggests donot support parameterised lookups.

Any other suggestion?

Time for upgrade Anisha

Regards

Suman Pramanik

Agree with what SumanPramanik has mentioned - "Time for upgrade Anisha"

NJ

"lookups within lookups" ("lookup filters") as I have badly explained above would still work in 7.5.3 I think

(this is _not_ using parameterised lookups).

I agree!

Upgrade is on the cards.

Have you tried what Dave has mentioned ?

" "lookups within lookups" ("lookup filters") as I have badly explained above would still work in 7.5.3 I think

(this is _not_ using parameterised lookups).

"

NJ

...if the values are all static (rather than NSQL derived) then a static-dependant-lookup might also be an answer.

yes static dependent lookup solved my requirement..

Thanks,