-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specific filter does not give correct results #149
Comments
Closed the issue, it cannot be reproduced on version 1.45. |
Reopend. New version: BE 2.0.0 FE 1.46. This specific filter does not work anymore. Last time (v2.0.0 1.45) I did get correct results... Weird that this specific filter does not work properly. Note: when opening from saved filters. Creating the filter one time does give correct results. |
@boris-arkenaar we discussed filters with incorrect results last tuesday. In this ticket you will find several examples. |
Issue is still present. I still do not know the exact cause. User applied filter on multiple Subcategory, Area, Status and Medewerker=Niet toegewezen. The result is either all signals or the results from the previous filter are shown. |
I can't directly reproduce this. Does it only happen when you select so many options per Subcategory, Area, Status? |
Yes, only the very extensive/large filters have problems. Note: the result is correct when you make an incidental filter. Only after opening a saved filter the results are incorrect. |
Additional information: Most likely, the filter/search request is too large. There is no error or warning message that informs the user about the incorrect result. |
One specific filter does not give the correct results. It either shows all signals or shows the results from the previous filter.
I was unable to determine a cause.
These are my conclusions so far:
Filter with incorrect results:
Could you please find out why this filter, the combination of chosen fields or the save and "Toon results" option does not work properly?
The text was updated successfully, but these errors were encountered: