Parameterized lookup - unable to select values in New UX


Article ID: 211637


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


A Parameterized lookup shows no values in the drop down list in the Modern User Experience (UX). The lookup works correctly in Classic Clarity. This may be reported for lookups using a dynamic query with a constraint.

Note: If you remove WHERE:PARAM:USER_DEF:STRING:PARAM_PROJECT from the lookup's query, the issue doesn't happen.


  1. Create a custom dynamic lookup (object: Task) with below query:
  2. Create a custom object as a sub object to the project object
    • Make sure the custom object is API Enabled
  3. Create a custom attribute on the custom object:
    • Select Data type of lookup
    • Associate the attribute to the lookup created above
    • Enter an API Attribute ID
    • Under Lookup Parameter Mappings select odf_parent_ID from the drop down for param_project
  4. Go to the Modern UX
  5. Add the new custom object as a module to a project Blueprint
  6. Create a new project and populate the project’s Blueprint as that updated in Step 5
  7. Create at least one milestone task on the project
  8. Go to the custom object's Module on the project
  9. Add the custom attribute created in step 3 to the column list
  10. Click + to create a new row and enter the required attribute details
  11. Search for values on the custom attribute or click on the drop down to try to select a value

Expected result: The attribute shows all milestones for the project as available to select from

Actual results: The drop down list is blank and no values can be selected

In the app-ca.logs, the following error shows:

ERROR 2021-03-29 14:41:05,767 [http-nio-80-exec-35] (clarity:admin:…:PPM_REST_API) LookupFilterParser :: The lookup [Custom_AttributeName] filter [((searchText startsWith '%') and (param_param_project = 5000001))] attribute[param_param_project] has invalid value [5000001].


This issue is caused by: DE60278 


Release : 15.8.1, 15.9, 15.9.1, 15.9.2



Fixed in 15.9.2 patch 1 and also targeted to be fixed in 15.9.3.