IBM Support

BiLog: Limits...QBR Record Limits

Technical Blog Post


Abstract

BiLog: Limits...QBR Record Limits

Body

 

image
I need to set limits when faced with these.  Knows as Fluffernutters, smooth, decadent peanut butter and sticky marshmallow topping on plain white bread form the ultimate comfort sandwich.  With a cold glass of milk, the number I can toss down is crazy high.
 
You may also need to stop your users from over-indulging by setting records limits when they create Ad Hoc or QBR (Query Based Reports.)  The creation process of ad hoc reporting is where users select the fields, application query, sorting and grouping that they want to apply to their unique custom report.   This is a very iterative process where the user goes back and forth between the design and execution of the report to form the end result they need.
 
During this creation process, because the user will be executing his ad hoc report multiple times, you may want to set record limits.   The record limits will force the user to utilize a filtered query instead of executing against all or a very large number of records in the database which can cause negative performance impacts.
 
To utilize this, a new property setting has been created called: mxe.report.adhoc.previewLimit.  This property setting applies to any QBR report as they are being created.   After a QBR report is saved, the property setting does not apply.
 
The key business rules on this property setting when the user clicks submit on the QBR Creation dialog: 
 
1.  If the user’s application record set + report filters < property setting value, report preview will occur.
 
2.  If the user’s application record set + report filters > property setting value, report preview will not occur.    In this case, the user is prompted with a message to reduce his query.

image

This is highlighted in the example here.  The user has an active application query of 430 records, but the QBR preview limit has been set at 45 records.   When the user begins creating his report and clicks Submit - he will receive a message that his application query exceeds the preview limit.   The user must then exit out of the QBR dialog, and reduce his application query before proceeding.

 
3.   If user clicks the "Save Report' on the dialog, and his application record set + report filters > property setting value, the QBR report will be saved.  However, the QBR report will NOT be executed and displayed in report viewer.
 
4.  This property setting is currently available via Maximo 7.5.0.3 Interim Fix 003, 7.5.0.3-TIV-MAM-IFIX003
 
This record limit functionality is similar to the enterprise report functionality detailed here where you can set the maximum limit by individual reports. 

For additional information on performance enablers for QBR reports, please review this previous Bilog entry  and video  recording which review setting user’s functionality privileges.   It is highly recommended that only a subset of your ‘power users’ be given the ability to create reports on the fly based on their Maximo skill sets and job requirements.  

Also, for a complete listing of report property settings, access this wiki page here

 

 

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11133637