search cancel

Changing a parameterized lookup via XOG to non-parameterized breaks the attribute in the MUX

book

Article ID: 203302

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Modifying a parameterized lookup via XOG to make it not parameterized breaks the attribute in the New User Experience (UX / MUX), and leaves an "orphaned" parameter mapping. This modification is not allowed via the UI. It may be working in one environment, but in another environment, it's not working even though you are using the same exact query.  Examples of attributes where this can be reported include:

  • Project category
  • Project Type

STEPS TO REPRODUCE:

  1. Go to Administration > Studio > Objects
  2. Create an object called Garment and API enable it for use on the Modern UX
  3. On the attributes list, create a string type attribute called: printmethod
  4. Add it to the object Properties and object List views
  5. Administration > data Administration > Lookups
  6. Create a Dynamic query lookup called "Garment Lkp" with the following query:

    SELECT
    @SELECT:garment.printmethod:[email protected]
     FROM ODF_CA_GARMENT garment
     WHERE @[email protected]
     AND (@WHERE:PARAM:USER_DEF:STRING:[email protected] IS NULL OR @WHERE:PARAM:USER_DEF:STRING:[email protected] = garment.name)

  7. Go to Administration > Studio > Objects > Project object
  8. Create a lookup type attribute (My Garment) and link it to the "Garment Lkp"
  9. On the Attribute Lookup Parameter Mappings, select "Name" as Object Attribute ID
  10. Add the attribute to the object Properties and object List views
  11. Go to Home > Custom Objects > Garment
  12. Create two instances of the object
    • Name:Garment A ID:Garment_A Printmethod: Garment A Printer
    • Name:Garment B ID:Garment_B Printmethod: Garment B Printer
  13. Create a project in Classic called Garment A
  14. On the project properties view, click on the My Garment attribute binoculars
  15. Garment A Printer value can be selected
  16. Do the same on the project list view. The lookup value is selectable
  17. Go to the Modern UX (MUX)
  18. Add the project attribute My Garment to a project blueprint
  19. On the Grid view add the column to it
  20. The Garment A value is selectable on both views.
  21. XOG out the lookup
  22. Change the lookup code from:

    SELECT
    @SELECT:garment.printmethod:[email protected]
    FROM ODF_CA_GARMENT garment
    WHERE @[email protected]
    AND (@WHERE:PARAM:USER_DEF:STRING:[email protected] IS NULL OR @WHERE:PARAM:USER_DEF:STRING:[email protected] = garment.name)

    TO

    SELECT
    @SELECT:garment.printmethod:[email protected]
    FROM ODF_CA_GARMENT garment
    WHERE @[email protected]

  23. Flush the Clarity caches
  24. On the Classic UI, using the same project, check the properties and list views
  25. As the parameter mapping has been removed both values can be seen: Garment A Printer and Garment B Printer
  26. Do the same on the Modern UX: Check the Project properties and grid view

Expected Results: As the parameter mapping has been removed both values can be seen: Garment A Printer and Garment B Printer 
Actual Results: No values can be selected. None is displayed

Environment

This can be reproduced in all Clarity releases

Cause

This issue is caused by DE62837. This happens if the Lookup was at one time in the past a parameterized lookup.

Resolution

Fixed in 16.0.1

Additional Information

See also: Lookups master KB for Clarity