Scheduled report displaying all DB data without filter conditions
We have configured custom filter section in the report definition and in runtime the values in the report are filtered based on the value selected in the custom filter section.But as per our requirement whenever we schedule the report,the filter values should be saved and the scheduled report should display only filter values but it is fetching all the values from DB.
To get this funcationality worked,one has to save the filter values and pass it to the report.But as the rules that are getting called for schedule are final,user is not able to modify the rules.
***Moderator Edit: Vidyaranjan | Updated SR details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I think you will need to create a separate version of this report for the scheduled runs, that uses property references as the values of the filter criteria, and has no custom filter section. As long as the property values are set when the scheduled run takes place, the report should be filtered correctly.
We want to schedule a saved report. The saved report uses Filter Page properties to display its results. While we open a saved report we perform property-set of the previously selected filter page properties in the pytemplatetree data transform (It is a data transform which calls when we open any report shortcut) so that the report will use the selected filter page properties and display the results accordingly. But while we schedule the same saved report we are not getting where to set those previously selected filter page properties so that the data displays accordingly. Since the filter properties are not set the report is taking all the data from DB.
One of the main activity that calls while we schedule a report is pxScheduleTaskWrapper. Since, it is a final rule we cannot set our Filter Page properties here.
I guess the approach you suggested is what we are trying but facing this issue. If your suggestion is different from our approach please suggest how to achieve that.