ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Creating virtual attributes from more than one master object results in unexpected behaviour

book

Article ID: 239389

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

An issue has been noticed with virtual attributes in a custom object, whose master object is the Investment object. Steps to reproduce it are as below.

  1. Create a custom object, as a child object of the investment object
  2. Create custom attributes of the following data type in the Project object:
    1. Money
    2. Number
  3. Create custom attributes of the following data type in the Service object:
    1. Money
    2. Number
  4. Create new virtual attributes, in the custom object created in Step 1:
    1. Master Object = Project 
    2. Attributes:
      1. Custom attributes from Step 2
      2. Planned Cost
      3. Planned Capital Cost
      4. Planned Operating Cost
  5. Navigate to a Project instance. Populate values against the following attributes, if not present already:
    1. Custom attribute of data type money from Step 2
    2. Custom attribute of data type number from Step 2
    3. Planned Cost
    4. Planned Capital Cost
    5. Planned Operating Cost
  6. Create an instance of the custom object from Step 1. Configure the virtual attributes from Step 4 in the List View. Observe values against these virtual attributes
  7. Create new virtual attributes, in the custom object created in Step 1:
    1. Master Object = Service
    2. Attributes:
      1. Custom attributes from Step 3
      2. Planned Cost
      3. Planned Capital Cost
      4. Planned Operating Cost
  8. Navigate to a Service instance. Populate values against the following attributes, if not present already:
    1. Custom attribute of data type money from Step 3
    2. Custom attribute of data type number from Step 3
    3. Planned Cost
    4. Planned Capital Cost
    5. Planned Operating Cost
  9. Create an instance of the custom object from Step 1. Configure the virtual attributes from Step 7 in the List View. Observe values against these virtual attributes
  10. Observe values against the same instance as in step 6, in a Project instance

Expected Results:

  1. Values in the master Project instance are shown in the virtual attributes of the Project object
  2. Values in the master Service instance are shown in the virtual attributes of the Service object

Actual Results:

  1. Values observed in step 6 disappear in step 10
  2. Values are duplicated against virtual attributes of the Project object, in step 9

Cause

This behaviour has been reported to Product Management through DE64779.

Environment

  • Version: 16.0.1

Resolution

A decision was made to not fix DE64779. Even though the UI allows this configuration, the code to support it in the backend was never implemented. There are no plans to support it in the Roadmap either.

It is recommended that a Portlet be used to view fields in a single view, or the Hierarchies in the Modern UX.