This content has been marked as final. Show 3 replies
This is unfortunately a trade off with multi-select OR navigation requests. The cleanest way to handle it that I know of is to:
1) In the URLs to remove filters (in your left hand navigation), add a token to the URL to indicate it is a "remove filter" action
2) In your web application, when you get the ENEQueryResults object back, check if the total number of records is zero
3) If zero, and the action was a "remove filter", display a message to the user that "removing XYZ returns zero results due to your other selections"
4) You can either display the zero results page at this point, or display the state prior to it - or even clear all filters apart from category
Thanks for the suggestion Michael. We are also thinking of clearing all the filters for now, but that would still mislead / confuse the user. Business does not want the user to see zero results. So its a tricky situation we are facing.
But ... zero results is the correct answer.
Maybe the best way of addressing this is to tell the user that for the combination of selections which they have made there are no results. And suggest how they can get results by making different selections.