When you use the filter control extension with serverside enabled the querystring param search gets populated with whatever you search for in the column filter control inputs. This is confusing if you try and use the global upper right search and the filter control search at the same time. I had to disable the upper right main search and ignore the param search= for now.
Easy to respoduce using browser dev tools > network.
In this example I have a 1 in the filter control input for id and 11 in the filter control input for cabinet, notice the search=11 which was the last entry. Even if you had TEST or anything in the main upper right search the search parameter gets overtaken.
?search=11&sort=cabinet&order=desc&offset=0&limit=10&filter={"id":"1","cabinet":"11"}
When you use the filter control extension with serverside enabled the querystring param search gets populated with whatever you search for in the column filter control inputs. This is confusing if you try and use the global upper right search and the filter control search at the same time. I had to disable the upper right main search and ignore the param search= for now.
Easy to respoduce using browser dev tools > network.
In this example I have a 1 in the filter control input for id and 11 in the filter control input for cabinet, notice the search=11 which was the last entry. Even if you had TEST or anything in the main upper right search the search parameter gets overtaken.
?search=11&sort=cabinet&order=desc&offset=0&limit=10&filter={"id":"1","cabinet":"11"}