Custom lookup became corrupted after changes to the lookup query via XOG

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

We made some NSQL code modifications in our lower environment, and upon XOGing it, the latest query was updated. However, the lookup became corrupted afterward.

Resolution

After reviewing NSQL query prior to the update and post it was determined that the column which was used as hidden key was updated.

Hidden key should not be changed/updated as it is used for mapping lookup values.