SUMMARY: After creating a Virtual Attribute on the "Team" Object to view a Project's "Cost Type", the Unfilled Allocations Portlet only displays the Cost Type for Projects, not Ideas. If you then try to create a second Virtual Attribute to view an Idea's "Cost Type", it works, but causes the Project Cause Type to stop working
STEPS TO REPRODUCE:
1. Create a Virtual Attribute for "Cost Type" to the Team Object. The referencing Object will be "Project".
2. Access the "Unfilled Allocations" portlet in "Home" then "Resource Planning" and the "Unfilled Allocations" tab.
3. On the portlet add the virtual attribute to the attributes in the results section, so you can see it in the grid.
4. Note at this time you will see the "Cost Type" only for Projects, but not Ideas.
5. Create another Virtual Attribute for the Team object, but this time using the referencing Object of Idea. Point to "Cost Type" again.
6. Go back to the portlet and add this new Virtual Attribute to the grid as well. You will notice that now you can only see the "Cost Type" for Ideas, Projects will have the value blank.
Expected Results: To have two attributes to display both the Cost Type for Projects and Ideas.
Actual Results: You can only see one or the other. It doesn't seem possible to see both at the same time.
Release : 15.6.1, 15.7, 15.8
Component : CA PPM SAAS APPLICATION
This problem is linked to defect: DE31851
There are more details for this defect in this document: https://knowledge.broadcom.com/external/article?articleId=97293
The information in that document states the following:
After careful review, it has been determined that this defect will not be fixed. Please reference the following link: CA PPM Defect Resolution Policy for more information.
For custom attributes: Create the attribute on the Investment object and then the data will show up properly in the list views for the subobject.
For out of the box attributes: The only workaround would be to create a custom attribute on the investment object and link that to the Idea and Project Type lookup (or applicable lookup). As long as the attribute ID is different then other objects, this issue should then not occur when you create a virtual attribute on the team object.