Anyone know what conditions cause the dialog box that says "A filter must be specified." to come up? I am joining two underlying views and cannot figure out why sometimes this comes up and other times it does not.
I also have this problem; it appears when the result of running the report is large. If this error message is triggered, you can still get the report to run by putting on a filter which does not actually filter out anything (!?). I experimented with a moderately large table of 9951 rows. If I select a filter that doesn't filter out any rows, I will still be able to produce a 199 page report containing 9951 rows.But I still do not know what is the maximum amount of data that causes this error message to be triggered. Also, this error message is a little vague.|||Has anyone got a clue for the reason of above behaviour? Its pretty annoying to see the filter pop-up coming up when you don't want to filter any data. One workaround is to create a dummy filter which won't actually filter any rows from the output.|||
well !
Got it! The Instance Selection property of an entity in the model determines whether filter must be specified.
No comments:
Post a Comment