Custom domains acting odd - wrong schema name post Jaspersoft 7.8 upgrade
search cancel

Custom domains acting odd - wrong schema name 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 have the wrong schema name in the TEST environment after upgrading to Jaspersoft 7.8.

Environment

Release : 15.9.1

Component : CLARITY Reporting

Jaspersoft 7.8 upgraded from 7.13

Cause

The domain is corrupt. 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

Resolution

  1. Check to see if there are any Ad hoc reports using the domain

    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

  2. If there are no reports using it, it can be deleted.

Additional Information