Unable to run imported report containing resources with absolute path

Issue:

We have exported reports and its dependencies from TIBCO JasperReports® Server 6.x and imported the reports into TIBCO JasperReports® Server 7.5. 

After trying to edit and run the imported report as a user (eg. jasperadmin) under the new organization, the following error appears to the user:

"There was an error on the server. Try again or contact site administrators. (ERROR UID: 8c6d4f7a-7dbb-4644-9db6-e07911accf55)" 

The ../WEB-INF/log/jasperserver.log file captured the following error:

2020-04-27T16:19:30,538 ERROR ErrorPageHandlerAction,https-jsse-nio-8443-exec-37:118 - Error UID 8c6d4f7a-7dbb-4644-9db6-e07911accf55
com.jaspersoft.jasperserver.multipleTenancy.MTResourceNotVisibleException: You may not access resources which do not belong to your organization.
...

Caused by: com.jaspersoft.jasperserver.multipleTenancy.MTResourceNotVisibleException: 
Path /organizations/<organization_name>/organizations/<suborg_name>/Data_Source/<DS_NAME> is not visible in organization context 

Note: The issue does not occur for the superuser account. 

Solution:

The error comes from a resource referenced from the report where there is an absolute path: 

/organizations/<organization_name>/organizations/<suborg_name>/Data_Source/<DS_NAME>

There were changes implemented in the TIBCO JasperReports® Server 7.x release where an absolute path referenced in report resource is no longer acceptable.

The solution is to update the affected resources to reference relative paths which is relative to the organization user.

In the TIBCO JasperReports® Server 7.5 Release Notes, the following statement was documented:

JS-34346: This release changes resource visibility constraints in multi-tenant deployments (that is, those that include more than one organization). 

The change disables certain cases of improper resource referencing, such as providing an absolute repository path (starting with the root organization) 

for a resource referenced in a report. If you have a reference to an image, a subreport, or other resource that has an absolute path (or uses a $P{} 

parameter that later resolves to an absolute path), the server returns an error. Please update such references to use path that are visible to users 

in the organization in question. Consider using relative paths, or use the public folder for reports used by multiple organizations. 

ref: 01861769