Team Allocations data provider throws : ORA-00904 invalid identifier on custom virtual attribute due to alias mismatch in filter
search cancel

Team Allocations data provider throws : ORA-00904 invalid identifier on custom virtual attribute due to alias mismatch in filter

book

Article ID: 424080

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

After upgrade from 16.2.3 to 16.3.3 your custom portlets based on Team Allocations started showing System Error in Classic and ORA-00904: "PRPROJECTID"."CUSTOM_FIELD": invalid identifier error in logs on a custom virtual attribute from investment

STEPS TO REPRODUCE

  1. Create a few custom portlets in Classic based on Team Allocations
  2. Add custom field in Investment object on Lookup String – static lookup
  3. Create virtual field in Team object to use the same custom investment field
  4. Also create a virtual field in Team object to a Project object Date field
  5. Add the custom fields to the portlet column layout
  6. Make sure there is a number of fields selected for Filter Layout
  7. Publish the portlet
  8. Add the portlet to a custom page tab on the Overview page
  9. Access the page

Expected Results: No error messages and the page to work correctly

Actual Results: System Error in Classic UI. In logs, error is thrown: ORA-00904: "PRPROJECTID"."CUSTOM_FIELD": invalid identifier

Environment

Clarity 16.3.3

Cause

DE180733

Resolution

In review by Engineering

Workaround:

  • Disable feature toggle APPLY_DB_ALIAS_FOR_VIRTUAL_ATTRS_DE78599 by running:
    • admin toggle-feature APPLY_DB_ALIAS_FOR_VIRTUAL_ATTRS_DE78599 0
  • Restart services or clear caches
  • Note: This change will revert the changes for Virtual attribute does not show data
  • We recommend to check if that applies to your setup

Other possible workarounds:

  • Remove all fields from Filter Layout
  • Or Create a second virtual attribute on team object