Unexpected behaviour Filter Query Results

GertV

Hi,

I have a query that shows active Members from an object that contains both active and inactive members.

When I run this query it initially shows the correct members. When I use the Filter Query Results and reduce the search to Members with Last Name Johnson, it shows me again the right results.

When I go back to Filter Query Results and choose Extend and leave all search fields blank, it shows me ALL records of the object, i.e. active and inactive members. The initially defined query is overlooked.

Is this the normal behaviour or a bug?

aware_support

This is a grey area - it's hard to say how the system should behave in this case.

GertV

Why is this a grey area. I don't see the logic of abandoning the initial query results.

ab042

Would this "grey area" also apply to security concerns?

For example, if we have a query that only allows a user to see their own records or restrict accounting records from being shown outside the active accounting period?

If so my vote would be to fix it ASAP OR turn off the ability to extend after search or whatever routine maybe causing this "grey area".

GertV

Yep that's exactly the point. My members are now seeing people listed as member that have long cancelled their membership. In this case it's not a real security issue, but in other cases it is much more dangerous.

aware_support

"Extend" can extend the original query - this is one of the reasons it is there (just like "Reduce" can reduce the original query).

If security is an issue here remove the "Extend/Reduce" option from the query results screen.

GertV

I can you your point. However how do you let users search in your query when you don't want them to extend over the initial limitations?

aware_support

There is no such functionality in the system now