ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Clarity: Query Dependent Lookup Values on the custom object module list page doesn't preserve the value 


Article ID: 195050


Updated On:


Clarity PPM On Premise



1. Login to Clarity and Navigate to Administration --> Object 
2. Create a sub object of Project and name it as aaa (example: AAA)
3. Create a Dynamic Query lookup called Lookup with below code 

 select @SELECT:cc.code:[email protected],[email protected]
from odf_ca_aaa cc
where @[email protected]
and (cc.odf_parent_id = @WHERE:PARAM:USER_DEF:INTEGER:[email protected])

4. Create a lookup attribute using the above created dynamic lookup 
5. Save the attribute and now set the Lookup Parameter Mapping to --Object ID--
6. Now Navigate to Modern UX and add the AAA object as module in your blueprint 
7. Navigate to AAA module list page and add the attribute Lookup Attribute
8. Create an instance of Dependency and fill it value for Lookup Attribute
9.Refresh the browser and now the Lookup Attribute value doesn't appear, however on the details layout the value remains 

Expected Results: The value of lookup attribute (Lookup Attribute) should be shown on the list page

Actual Results: The value of lookup attribute (Lookup Attribute) disappears 




This is a potential defect DE56341 and currently under investigation by our engineering team 


Release : 15.8, 15.8.1 

Component : CA PPM STUDIO


Workaround: See the value of lookup (Lookup Attribute) from the details fly out page until the defect is fixed