Filters not taking the modifed values of the grid

Discontinued products Uncategorized discussions
#1


Hi



I have a problem with using filters in grid. The values which has been modified using grid.setValue() does nt seem to take effect when i filter using filterBy().



step 1: grid.filterBy()



step:2 grid.setValue()



step 3: grid.filterBy(same filter) - should show the results with modified values but it shows the old values



I set the preserve parameter to true. But the second time i apply a diff filter criteria, it tries to filter within the previously filtered values.



 



How can i achieve this? I want to modified values of the grid to reflected in the subsequent filtering without having to reload the grid.



Thanks for your help.



Gayathri



 

#2

Unfortunately we cannot reproduce this issue locally. What version of dhtmlxGrid do you use?

#3


Hi,



Gayathri is my colleague. We both are working on this problem.



We were using the version v.2.1 build 90226. Now I have updated it to v.2.5 build 090904.



In this version this problem is solved partly. Now wer are facing same problem in conjuction with paging.



After filtering, rows on the current page retains changed values but other pages changed row values are lost.



Can you please help us with this?



Thanks



Jalpa



 

#4

Please contact us directly at support@dhtmlx.com

#5

Hello togehter,
i’ve got the same problem like you described in the first post. When I change cells with help of the setValue method in Grid in filtered state with SmartRendering activated, and set the filter to this value right after, the rows aren’t displayed. Setting the filter to the old value of the cell (before change), the row is displayed.
We use dhtmlxGrid v.2.1 build 90226 professional, is there any fix on this issue without updating to the newest version?
Thank you

#6

Contact us directly at support@dhtmlx.com, there is no separate patch, but I think we will be able to provide some kind of fix.

#7

Hi, thanks for the email, it works like a charm in normal grid. But in treegrid the same issue persists, perhaps this can also be fixed by such a small change?