Custom Lookup attribute does not display values in Status Report

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

A lookup based attribute might display an empty list of values for the Status Report object in the Modern UX.
  

STEPS TO REPRODUCE: 

1. Create a new custom object in Studio.
custom object: co_test

2. Just create one attribute for the new object, co_test.
attribute: ca_test 

3. Add a few instances for this new custom object.

4. Create a new lookup of type Dynamic Query.
lookup: lookup_test

5. The lookup will just get the values for the instances of the custom object, co_test:
select id, name, code, ca_test
from odf_ca_co_test
where @FILTER@

6. Create a new attribute on the Status Report  object.
attribute: sr_test

7. The attribute sr_test will by of data type lookup, and will be associated to the new lookup created before, lookup_test.

8. Make the new attribute of the status report, sr_test, API enabled (available in MUX), filling its API Attribute ID (z_sr_test).

9. Add the attribute sr_test to some Status Report on a Project in the Modern UX.

10. Try to select/displaye the values of the sr_test attribute.

 
Expected Results: The attribue to display the list of values for the lookup, corresponding to the values for each instance of the custom object.

Actual Results:  The attribute does not display any value, -- None- -

Environment

Clarity PPM 16.x

Cause

This is caused by DE79989

Resolution

After being reviewed by SE, this is considered to be working as design.

As a recommendation/guideline, the @SELECT@ tag should be used on the fields/columns in order to make them work the way they are supposed to work (one of those is the auto suggest functionality).

The query in this case should be rewritten as follows:

select @SELECT:CO_TEST.ID:ID@, @SELECT:CO_TEST.CODE:CODE@, @SELECT:CO_TEST.CA_TEST:CA_TEST@
from odf_ca_co_test CO_TEST
where @FILTER@

Workaround: Add the value in the Status Reports for the Project in Classic UX.