Custom Report Error Messages

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

8.4

Please share any images or screenshots, if relevant.

image
image1342×285 62.3 KB

Please share any other relevant files that may be required (for example, logs).

sailpoint.tools.GeneralException: Result set was limited. Please update report filters to narrow results or submit an IT request for a larger data export.

Share all details about your problem, including any error messages you may have received.

Within our custom JavaDataSource report classes, we throw a custom exception when a user attempts to run a report with more than a defined number of returned records (above). This is to prevent users from generating a report that could hog resources thus impacting performance for other users.

We do this through QueryOptions.setResultLimit() and /or SQL query SELECT TOP # FROM...

In the case where either of these limits is reached, we want to terminate the report and inform the user why.

Initial thought was throwing a custom exception with the error message above and have it displayed in place of the default ‘serious error occurred’ but if there’s a more graceful way please let us know.

2

Hi
Instead of throwing an exception you can try returning a row with a message like for eg :

Map warningRow = new HashMap();
warningRow.put("message", "Too many results. Please apply filters.");

List results = new ArrayList();
results.add(warningRow);

return results;

let me know if this works

3

We do not want the report task to be shown as completed successfully in this case if possible.

4

option 1) You can proceed records by limit. Check max limits and trigger notification within report.

  1. Don’t show report. Terminate it. You can configure Mail Notification/Audit for Limit Issue
5

  1. How can we send a notification from within the report? The Monitor class doesn’t appear to have a method and I’m not sure how to get access to the parent TaskResult object from the report run. Is there another method?

  2. How do we terminate the report within the code without it showing as completed successfully?