Custom (not out of the box) Domains acting odd - wrong schema name in TEST environment post Jaspersoft 7.8 upgrade

book

Article ID: 212330

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Custom (not out of the box) Domains acting odd - wrong schema name in TEST environment post Jaspersoft 7.8 upgrade

Environment

Release : 15.9.1

Component : CLARITY PPM Reporting

Jaspersoft 7.8 upgraded from 7.13

Resolution

Normally. a domain that has been imported from a different environment, can have its domain corrected by going to Advanced Reporting > Manage > Update Domain Schema

However, this domain was corrupted. Fortunately, we could see there were no Ad Hoc reports using it.  So, it will be deleted.

SELECT f.uri||'/'||r.name AS Domain_Path, f2.uri||'/'||r2.name AS DomainAdhocReport 
FROM jidomaindatasource dINNER JOIN jiresource r ON r.id = d.id
INNER JOIN jiresourcefolder f ON f.id = r.parent_folder
INNER JOIN jireportunit u ON u.reportdatasource = r.id
INNER JOIN jiresource r2 ON r2.id = u.id
INNER JOIN jiresourcefolder f2 ON f2.id = r2.parent_folder
ORDER BY Domain_Path, DomainAdhocReport


Additional Information

https://community.jaspersoft.com/wiki/identify-all-adhoc-report-units-related-domain

Please see post upgrade steps here:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/clarity-project-and-portfolio-management-ppm-on-premise/15-9-1/installing-and-upgrading/upgrade-clarity-ppm/Upgrade-to--Jaspersoft-7_8-and-Migrate-Advanced-Reporting-Content.html