Custom Attribute Causing Error in Ad-Hoc Jaspersoft Report

book

Article ID: 131433

calendar_today

Updated On:

Products

CLARITY PPM FOR ITG CLARITY PPM FEDERAL Clarity PPM SaaS - Application Clarity PPM On Premise

Issue/Introduction

We have a custom lookup attribute that has been added to the Clarity PPM Project object which we are sending to Data Warehouse (DWH) for reporting, but when adding them into an ad-hoc Jaspersoft (JS) report, we are seeing three different options available for selection on the same attribute name. Two of them seem to work properly, returning the attribute key and value respectively, but the third returns "An error occurred while performing the previous request" when trying to add it to the list of selected values.

We tried removing the attribute from DWH, and after running the Load DWH job two of the fields no longer appeared in JS, but the one giving an error still shows.

Environment

Release:
Component: PPMJSP

Resolution

On Premise customers:

Run the following command: admin content-jaspersoft csk restoreDomains -userName <superuser> -password <superuser>

SaaS Customers:
Please open a case with support for assistance

Additional Information

See KB000009869 - List of Jaspersoft Commands in accordance with Clarity PPM Version