Custom Dynamic Lookup Saves Wrong Value

book

Article ID: 134917

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

When selecting a value on a custom dynamic lookup field, a different value than was selected appears to be saved on the object instance. For example, value A is selected, but once the Save button is clicked to save this value, value B shows as selected on this field. 

Environment

Release : All PPM Releases

Component : CA PPM SAAS STUDIO

Resolution

The issue occurs when the Hidden Key on the lookup is set to Code and the Default Sorting Column selected is Name (under Administration - Lookups). 

To get the correct value to display when clicking on Save, either: 

1. Create a new lookup with the same NSQL, but with Name as the Hidden Key (instead of Code)

OR

2. Use the existing lookup, but change the Default Sorting Column from Name to Code (under Administration - Lookups - <Application Lookup> - Browse Window tab)