Last Updated: 11 Apr 2022 07:37 by ADMIN
Created on: 30 Mar 2022 15:47
Category: FileManager
Type: Bug Report
FileManager toolbar search filters produce inconsistent results when navigating treeview

I am running into inconsistencies when using the toolbar Search input of a File Manager object after navigating to new folders.  

Simple dojo for reference - https://dojo.telerik.com/aPOtiXex/2

Steps to reproduce

  1. Click on "Folder1" in the treeview.
  2. In the Toolbar Search, enter the text "Sub 1001".  This will correctly filter the displayed items.
  3. Click on "Sub 1001" in the treeview.  Notice that the search filter is still in place, but that it is not applied to the current folder view.
  4. In the Toolbar Search, remove the text 1 character at a time.  Notice that as you remove characters in the Search input, the filter IS applied to the current folder view.  Continue removing characters until the Search input is empty.
  5. Click on "Folder1" in the treeview.  Notice that the contents of the folder are STILL filtered as if the Search filter was "Sub 1001", even though Search input is currently empty.
  6. In the Toolbar Search, add 1 space character, then remove it.  Notice that this finally clears the filter applied to the folcer in step #2.

I am not sure what the best answer for this scenario would be.  Maybe navigating to a new folder should clear the search filter criteria in the toolbar and clear any applied filter criteria to the previous folder?  Or maybe the toolbar search input should be reset to accurately reflect the current applied filter for the folder on navigate?  Something good for your dev team to discuss, but it is clear that the current implementation will create some confusion for users.

Posted on: 11 Apr 2022 07:37

Hello, Kevin,

Thank you for sharing your improved solution as it will help other users suffering from the same issue.

Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Posted on: 04 Apr 2022 14:55


Using your modified example which clears the search input onNavigate, and the additional setTimeout execution of the search command, I did find a usable solution eventually.

Here is another modified dojo that does not produce a js error if you happen to be using a remote data source.

Posted on: 04 Apr 2022 11:30

Hello, Kevin,

Thank you for reporting the behaviour.

I have converted this thread to a bug report which you can track in our Feedback Portal. I have modified the example with the workaround to reset the search input value in the navigate event. If you prefer to apply the search value when you open the folder, please use the snippet below instead:

              e.sender.executeCommand({command:"SearchCommand", options:{field:"name", operator:"startswith", value: $("[title='Search']").val()}})

As a small token of gratitude for reporting the bug, I am updating your Telerik Points.

Let me know if you have any further questions.

Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.