With batch editing, I lose changes when I update the grid filter.

[Dermot Heslin]

I have a grid with batch edit. One record is edited, changes not saved.

I then click on a filter and select one item from the filter:

I am given a warning about unsaved changes. However, the grid has already been filtered.

[Dermot Heslin]

Grid with edit:

[Dermot Heslin]

Filtering:

[Dermot Heslin]

Warning with grid already filtered:

[Dermot Heslin]

Filtered grid after I click cancel (my edit is gone):

[Aishwarya Rameshbabu]

Hi Dermot Heslin,

Greetings from Syncfusion support.

We have conformed the reported scenario as a bug from our end and logged it as “Unsaved Batch Changes Are Lost Upon Filtering in the Grid”. Thank you for taking the time to report this issue and helping us improve our product. At Syncfusion, we are committed to fixing all validated defects (subject to technical feasibility and Product Development Life Cycle ) and will include the defect fix in our upcoming patch release which will be rolled in the end of March, 2025.

You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through the below link,

Feedback: https://www.syncfusion.com/feedback/66057/unsaved-batch-changes-are-lost-upon-filtering-in-the-grid

Disclaimer: "Inclusion of this solution in the weekly release may change due to other factors including but not limited to QA checks and works reprioritization".

Regards,

Aishwarya R

[Aishwarya Rameshbabu]

Hi Dermot Heslin,

Due to the complexity of the issue, our team requires additional time to develop a comprehensive solution to maintain the stability and performance of our product. Consequently, we will address the reported problem regarding ‘Unsaved Batch Changes Are Lost Upon Filtering in the Grid ‘ and implement the fix in our upcoming patch release, scheduled for April 1st, 2025. We greatly appreciate your understanding and patience during this period.

Regards,

Aishwarya R

[Aishwarya Rameshbabu]

Hi Dermot Heslin,

We are glad to announce that, we have included the fix for the issue “Unsaved Batch Changes Are Lost Upon Filtering in the Grid” in our 29.1.35 release. So please upgrade to our latest version of the Syncfusion package to resolve the reported issue.

Root Cause: The filtering action prevention mechanism did not function as intended, causing it to return the next function associated with the object's value, which led to the execution of subsequent code.

Solution: The issue has been resolved by implementing a method that prevents the filtering action by returning 'false'.

Feedback: https://www.syncfusion.com/feedback/66057/unsaved-batch-changes-are-lost-upon-filtering-in-the-grid

We thank you for your support and appreciate your patience in waiting for this release. Please get back to us if you need any further assistance.

Regards,

Aishwarya R

[Dermot Heslin]

Hi there

I have noted that while behaviour has changed, it is still not working as expected. Please see my comment in the feedback: 

[Santhosh Iruthayaraj]

Hi Dermot Heslin,

The live demonstrations on the Syncfusion website are updated periodically; however, they do not reflect the latest fixes introduced in the weekly patch releases. Therefore, we recommend upgrading your Syncfusion package to the version 29.1.35 or to the latest version to resolve the reported issue.

Please refer to the attached sample, which uses the updated version, along with a video demonstration that shows how filtering is prevented when the cancel button is clicked in the batch edit confirmation dialog.

Sample and video demonstration: Please find in the attachment.

Please get back to us if you need any other assistance.

Regards,

Santhosh I

Attachment: sampleanddemo_bda3c7a2.zip

[Dermot Heslin]

Hi there

Thank you for your reply. I can see that it is working fine in the sample attached, but it is not working in my code. I am using Syncfusion.E2J.AspNet.Core, version 29.1.37. The sample you sent was using Syncfusion.EJ2.Javascript and Syncfusion.EJ2.MVC5 - could this be the issue?

Before filter:

By the time the warning box appears, the filter is already in place (now there are only 2 rows), and edit is lost:

[Dermot Heslin]

I am realising that perhaps I initially used the wrong label on the thread - I see I posted under MVC. My issue is in AspNetCore.

Thank you

Dermot