search cancel

MUX shows incorrect lookup value but shows correct one in Classic


Article ID: 144864


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


  • Happens when there are similar name and IDs with OBS.
  • If two values in a dynamic query lookup start with the same first character in the name and the IDs are similar, when selecting the value in the New UX seems to default to the first value it finds alphabetically.
  • The Clarity PPM New UX shows incorrect lookup value but the same lookup value shows correctly in classic view.
1) XOG in simple OBS.
<NikuDataBus xmlns:xsi="" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_obs.xsd">
  <Header action="write" externalSource="NIKU" objectType="obs" version=""/>
    <obs code="Test" isSecurity="false" name="Test">
      <level depth="1" name="Test1"/>
      <level depth="2" name="Test2"/>
      <unit code="TestA" name="TestA">
        <unit code="test23" name="ABCD"/>
        <unit code="test2" name="ADBC"/>
    <Object type="obs"/>
    <Status state="SUCCESS"/>
    <Statistics failureRecords="0" insertedRecords="0" totalNumberOfRecords="4" updatedRecords="0"/>

2) Create new Dynamic query lookup and paste the nsql:
@SELECT:u.unique_name:[email protected],[email protected],
@SELECT:u.last_updated_date:[email protected]
from prj_obs_units u, prj_obs_types t
where u.type_id =
and u.depth = 2
and t.unique_name = 'Test'
and u.unique_name is NOT NULL
and @[email protected]

3) Create new attribute on Investment object with Data Type - Lookup - String and assign the dynamic query lookup from step 2.

4) In new UX add the attribute to project blueprints in the new ux Project Summary section.

5) Go to a project in the new ux and see if the values stick in the lookup field in the UI.

Expected behavior: Selecting either value for the attribute in New UX and the value should stick in the UI.
Actual behavior: Value always goes back to the first value it finds alphabetically.


Release : 15.7.1

Component : CA Clarity PPM Studio


This is caused by DE53429


This issue was reviewed determined it would not be fixed. See workaround below.

Workaround 1: Avoid using name and the IDs are similar.

Workaround 2: Avoid using name and the IDs are similar.

  1. Log in with a user with Admin rights
  2. Go to Administration -> Data Administration -> Lookups
  3. Search for the lookup that has the issue
  4. Go to the Browse Window
  5. Scroll down to the list layout section
  6. Change the Default sorting column value to unique_name