Identify All AdHoc Report Units Related to a Domain

Jaspersoft Community 'Read-Only' as of July 8, 2022

Transition to New TIBCO Community Just Weeks Away

You can still search, review wiki content, and review discussions in read-only mode. Please email community@tibco.com with questions or issues requiring TIBCO review or response.

The following SQL query will help user to identify all report units related to a domain in JasperReports Server repository profile data source:

SELECT f.uri||'/'||r.name AS Domain_Path, f2.uri||'/'||r2.name AS DomainAdhocReport FROM jidomaindatasource d
INNER 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

This query can be used to assist in the effort to fix broken AdHoc Domain reports as the result of Domain changes.

Once all report units for a modified domain are located in the repository, users can export the affected domain AdHoc report units, and manually change domain fields in the following jrxml.data files for the AdHoc view/report units to match the modified domain:

adhocJRXML.data
stateXML.data
topicJRXML.data


After changes are made, users can run js-import job with update to load modified AdHoc report units back to the repository to make the AdHoc reports work again using modified domain.


TTC(37667/20130917)

Feedback