Virtual field displays blank in the Task object

Products

• Clarity FedRAMP
• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When the task object contains virtual attributes from two different objects and the parent object attributes have the same ID, the virtual field is populated only for one of the parent object task. The second object task virtual field displays blank.

STEPS TO REPRODUCE:

1. Administration > Data Administration > Lookups
2. Create a static list lookup called "My Status"  with values OK and KO
3. Administration > Studio > Objects > Project object > Create an attribute "My Status" (z_status) linked to the "My Status" lookup
4. Administration > Studio > Objects > "My Custom Investment" object > Create an attribute "My Status" (z_status)linked to the "My Status" lookup
5. Administration > Studio > Objects > Task object > Create a virtual field from each of the attributes above: "My Project Status" and "My Custom Investment Status"
6. Create a project instance and populate the "My Status" field
7. Create a task on the project and display the "My Project Status" and "My Custom Investment Status"
8. Create an instance of "My Custom Investment" investment and populate the "My Status" field
9. Create a task on the "My Custom Investment" and display the "My Project Status" and "My Custom Investment Status" 

Expected Results: The "My Custom Investment" object instance task displays its value for the "My Custom Investment Status" field. The Project object instance task displays its value for the "My Project Status" field.

Actual Results: The "My Custom Investment" object instance task displays its value for the "My Custom Investment Status" and "My Project Status" attributes. The project object instance task displays NO value for the "My Project Status" field.

Environment

Clarity 16.2.2 and higher

Cause

This is caused by a "column name collision" in the derived attributes SQL that Clarity generates for the task object.

When you create z_status on Project and z_status  on "My Custom Investment", both custom lookup attributes are stored in the same extension table ODF_CA_INV, in the same physical column z_status . This is Clarity's normal behavior — all investment type custom attributes share that table, differentiated only by which investment row they belong to.

Resolution

As of Clarity 16.2.2 a feature toggle was introduced to handle these scenarios where an attribute derives from multiple parents with the same column name.

In order to enable this feature run the following command on the Clarity server:

admin toggle-feature APPLY_DB_ALIAS_FOR_VIRTUAL_ATTRS_DE78599 1