There is known issue with AdHoc reports in a multilingual environment.
It works like this.
A user, who is not using the Maximo primary language, creates and saves an Ad Hoc report.
In doing so, the user enters a report description. This is a required field and and is part of the search index for this report in the Select Actions / Run Reports window.
The problem is that there is no Report Description entered for the Primary version of the report entry. If a user opens the Select Actions / Run Reports window in the primary language, they will see an error and be unable to search the report list.
There are a couple ways to handle this.
If you do not have a lot of users creating AdHoc reports, the Administrator can add the Report Descriptions in Report Administration. If this task becomes too much to handle, you can create an Automation Script that will automatically populate the Primary Language Report Description.
Here are the values for creating this script.
Script Language: jython
Log Level: ERROR
from psdi.mbo import MboConstants
from psdi.security import UserInfo
userLang = mbo.getUserInfo().getLangCode()
# If the current user is not a base language user, set a value on the base language description
if (userLang != baseLang):
mbo.setMLValue("description", baseLang, mbo.getString("reportname"),MboConstants.NOACCESSCHECK)
This Script is specifically targeted the AdHoc issue. It is only triggered when saving a new report (as specified by the Add Option in Launch Points)
The Script uses the reportname as the default description. This could be modified if you prefer.