In working with large data sets, it takes a long time to set up the queries and then apply them to the model, just to do some testing or basic report construction. While it is possible to filter the query to limit the data loaded in, when it comes time to publish, I have to go back to the query, remove my filter, then apply the change. I would like to see some kind of smart filter applied that can be ignored when the report is published so that I don't have to wait every time I need to make a change with something.
3 Comments
- At present with any change made you are forced to refresh data before you publish otherwise the changes will not be published. This can be very time consuming and resource intensive for large queries particularly as they end up running twice - once locally and again after the report is published. It is particularly frustrating when running on a low spec PC (e.g. tablet). Please allow for query changes to be published without having to refresh data first.
- My workaround is to incorporate a parameter into the query that can filter the data. After publishing the report, I log into the web interface and update the parameter to unfilter the data and refresh the data set.
- Status added:Needs Votes
