Date Entered and Date Modified list view filters not working #10395
Labels
Area:Search
Issues & PRs related to all things regarding Search
Priority:Important
Issues & PRs that are important; broken functions, errors - there are workarounds
Severity: Major
Significant impact/severe disruption
Status: Team Investigating
Labels for issues in which the Core Team are investigating / Intend to Investigate
Type: Bug
Bugs within the core SuiteCRM codebase
Issue
I applied the current 7.14.3 update and have also tested on a new installation.
Since at least this update when we set a list search filter (either advanced or basic) using the Date Entered or Date Modified fields, the results won't be correct.
I've pinpointed the cause to a code change in the ./include/SearchForm/SearchForm2.php file related to this commit:
serhiisamko091184@a24b68d
If we comment that line again the filters work as expected.
Expected Behavior
When using a date entered or modified filter, the results should be filtered by that date. e.g. I use the calendar to choose yesterday's (or tomorrow's) date for the date created field, so it shouldn't show records created today.
Actual Behavior
Today's records are shown.
Possible Fix
Deleting the line from this commit fixes that issue, but indeed the underlying issue that the commit was trying to fix won't work again.
The commit doesn't explain why to fix one module this line is added without affecting other modules.
Although I believe it has more to do with the way the date is changed between choosing it in the calendar and how the data in the backend is processed.
I added a custom date field (without range) and it seems to work.
It remains unknown to me if this affects custom date filters with range enabled.
Filtering using the included expected closing date for the opportunity field seems to also work in a new install.
Steps to Reproduce
Context
Since I was able to reproduce using a new install and this is a default and very common field to use, I believe it might be a high priority bug. I have commented the line directly on the core file for now as a tentative workaround.
Your Environment
The text was updated successfully, but these errors were encountered: