Hi,
we have problems with the SfTreeGrid for server-side Blazor (20.1.0.61). In the attached example our datasource contains an ObservableCollection with items implementing INotifiyPropertyChanged
(as described here: https://blazor.syncfusion.com/documentation/common/data-binding/data-updates).
The data is updated via a timer and everything works fine.
Here are the problems:
1.) if we click on a row in the SfTreeGrid, the update via INotifiyPropertyChanged immediately stops working.
2.) if we use "Syncfusion.Blazor.Grids.SelectionMode.Cell" instead of "Syncfusion.Blazor.Grids.SelectionMode.Row", INotifiyPropertyChanged doesn't even start working.
Hi Ralf,
Thanks for contacting syncfusion forum.
We are working on this query with high priority. And we need time to validate the issue and will update you with further details by 30th June 2022. Until then we value your patience. Meanwhile, we will contact you if any details are required.
Regards,
Pon selva
Hi Ralf,
Thanks for your patience
On further validation, we have considered the reported issue (“TreeGrid doesn't update data with PropertyChange after Row or Cell Selection”) as a bug. 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 technological feasibility and Product Development Life Cycle) and will include the fix in our upcoming patch release which is expected to be rolled out on 20th July 2022. Until then we appreciate your patience.
You can now track the current status of your request, review the proposed resolution timeline, and contact us for any further inquiries through this link.
Note: To view the above feedback, kindly login into your account.
Regards,
Pon selva
Hi Ralf,
Sorry for the delayed response.
While fixing this issue, we could see that the reported issue reproduced from our dependent component. So, we forwarded this issue into our dependent component to fix. We would include the bug fix in our upcoming weekly patch release, which is scheduled to be rolled out on 30th August 2022. Until then we value your patience.
Regards,
Pon selva
Hi Ralf,
Sorry for the delayed response.
Due to some unforeseen circumstances, we could not include the reported issue as promised. So, we have planned to include this in our upcoming volume release which is expected to be rolled out on September 21st , 2022.Until then we value your patience.
Regards,
Pon selva
Hi Ralf,
Sorry for the inconvenience caused.
Due to some unforeseen circumstances, we could not include the reported issue as promised. So, we have planned to include this in our upcoming volume release which is expected to be rolled out on 12th October 2022.
Until then we appreciate your patience.
Regards,
Pon selva
Hi Ralf,
Sorry for the delayed response.
Due to some unforeseen circumstances, we could not include the reported issue as promised. So, we have planned to include this in our upcoming patch release which is expected to be rolled out on 26th October 2022 without further delay. Until then we value your patience.
Regards,
Pon selva
Hi Ralf,
We appreciate your patience.
Kindly get back to us for further assistance.
Regards,
Pon selva
Hi Pon Selva,
thanks for fixing this issue.
Regards,
Ralf
We are glad that the provided solution helped to solve the issue. Please get back to us fur further assistance.
We are marking this ticket as solved.