Issue in Multivalued Lookup whose values depend on a Single valued lookup

Document ID : KB000074005
Last Modified Date : 10/04/2018
Show Technical Document Details
Issue:
Scenario:
How does a parametrized lookup behave when this is single or multi-valued lookup.
The out of the box financial location attribute is a dependent lookup based on the financial department.
Lets create a copy of the location attribute, but set this one as a multi-valued lookup and compare behaviors. 
 
Steps To Reproduce:

1. Go to 'Administration' > 'Objects' > select 'Project' object > click on 'Attributes' tab
 
2. Create a new attribute called 'loc2' with following details: Data Type: Multi Valued Lookup – Number, 
Lookup: Location browse (Location Browse ID: DPT_PARENT_LOC_PARAMETERIZED)

User-added image

User-added image
3. Add the 'loc2' attribute to the layout together with the Deaprtment and Location fields to compare the behavior.

4. Select 'Business Operations' for the Department field

5. Select 'Chicago' for the out-of-the-box 'Location' field that’s already there

6. Select 'z' for the 'loc2' field > Click Save and Return

User-added image

7. Change the Department field to 'Development', you will see that the 'Location' field goes blank but it doesn’t for the 'loc2' field.
The 'loc2' field still displays 'z'.
Here the first behavior change. The multi-valued lookup value is not erased when the base Department lookup is blanked out.  

User-added image

8. For the Location, you will also see 'z' listed as well, now select Sydney > click 'Add'

User-added image

9. You now see ‘z’ and Sydney

User-added image

10. The initially selected values remain and the newly added values get added to the selection 
    You need to explicitly click on the 'x' icon to remove the initially added values. These do not get deleted, when the base Department field value has been removed 

Expected Result: Single value lookups and Multi-values lookups to behave consistently
Actual result: The behavior when using Multi-values lookups is different
Environment:
Any CA PPM release
Resolution:
MVL lookups and lookups use different tables and that is why behaviors are different.
You need to explicitly click on the 'x' icon to remove the initially added values. These do not get deleted, when the base Department field value has been removed

User-added image