Issue with updating values on a filtered grid

Posted by: jkim on 12 May 2020, 6:18 am EST

  • Posted 12 May 2020, 6:18 am EST

    I was wondering what the best practice is for editing a value you are currently sorting on? Whenever I try to edit the value, it gets removed from my list and defaults to the next highlighted/selected row.

    I am currently using the flex-grid-filter
  • Replied 12 May 2020, 6:16 pm EST

    Hi Jason,

    It seems that your issue is that when you have applied filtering and if you edit any item, this item is filtered out as soon as the edit ends.
    If this is your issue, then you may use the CollectionView's refreshOnEdit property to prevent this behavior:
    flexGrid.collectionView.refreshOnEdit = false;

    If this does not resolve the issue, can you please explain more about the issue?

    API: https://www.grapecity.com/wijmo/api/classes/wijmo.collectionview.html#refreshonedit

    Regards,
    Ashwin
  • Replied 13 May 2020, 6:34 am EST

    Thanks for the reply Ashwin. I will give this a try and let you know if it resolved the issue.
  • Replied 22 October 2020, 2:05 am EST

    Hello Ashwin,
    Thanks for the solution. But in my case i have set flexGrid.collectionView.refreshOnEdit = false; But after running the application i have and error saying refreshONEdit is undefined. Please suggest.
  • Replied 22 October 2020, 3:08 pm EST

    Hi Ananth,

    Have you set the refreshOnEdit property the same as I have added or is there any other way you have implemented? Also, this property was added in the 5.20193.637 version. So, before this version, you cannot use this property.

    ~regards
  • Replied 22 October 2020, 4:04 pm EST

    Hello Ashwin, Your reply has soothed me. But to my surprise we are using An older version of 5.20172.334. Could you please help me how to resolve this issue in these versions?
  • Replied 25 October 2020, 2:34 pm EST

    Hi,

    This behavior not possible in the provided version. To accommodate the refreshOnEdit property, we had to change the internal design of the CollectionView because it could not be achieved using the previous API.

    We are sorry for the inconvenience but we hope you understand.

    ~regards
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels