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:
STEPS TO REPRODUCE:
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)
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)
SELECT
@SELECT:garment.printmethod:[email protected]
FROM ODF_CA_GARMENT garment
WHERE @[email protected]
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
This can be reproduced in all Clarity releases
This issue is caused by DE62837. This happens if the Lookup was at one time in the past a parameterized lookup.
Fixed in 16.0.1
See also: Lookups master KB for Clarity