Good afternoon,
I'm using the multiselect component and the virtualize stopped working in versions after 26. Before i select a value everything seems ok even when i scroll down.
If i select an item or apply a filter and then scroll down it will show what is displayed in the image "Version 29" that i sent in the zip folder. I specify the scroll down because the error occurrs when the scroll calls the api in the virtualize.
Any help with this problem would be appreciated.
Hi Francisco Fernandes,
Thank you for reaching out to us.
We have created a simplified sample based on the provided code snippet and noticed an issue where the data does not load correctly in the popup after searching, selecting an item, and scrolling. For your reference, we’ve attached a sample and included a video illustration below to demonstrate the behavior.
Sample: https://blazorplayground.syncfusion.com/VDBoNArQpwLSOYvT
Could you kindly confirm whether you’re experiencing the same issue on your end? Additionally, if you’ve encountered any other problem, please share any further details or observations you may have.
We appreciate your time and understanding.
Regards,
Priyanka K
Yes, that's exactly my problem.
Hi Francisco Fernandes,
We have considered this issue "Data is not loaded properly after we search and select an item when Virtualization is enabled" as a bug from our end, and the fix for the issue will be included in our upcoming weekly release which is expected to be scheduled at the end of April 2025.
You can now track the status of the feedback through the below link,
Feedback link:https://www.syncfusion.com/feedback/66688/data-is-not-loaded-properly-after-we-search-and-select-an-item-when-virtualization
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,
Priyanka K
The issue “Data is not loaded properly after searching and selecting an item when Virtualization is enabled” has been resolved in the v29.1.40 release of our package. Please update to the latest version to apply the fix and resolve the issue in your application.
Rootcause:
Previously, after filtering and selecting a value, the totalCount was incorrectly updated with the count of the main data source. This caused the virtual track element to calculate an incorrect height, which led to the observed behavior.
Release Notes: https://blazor.syncfusion.com/documentation/release-notes/29.1.40?type=all#multiselect
Thanks, that problem has been solved. Now I've noticed another problem with the Query.
I have .Take(100) and when the request is made for the first time it is right, but then in the other requests it always comes to 30 and SelectAll doesn't work either, it only selects 30 items and not all of them.
Hi Francisco Fernandes,
Sorry for the delay. We have considered this issue "Request is not send based on the query take value all the time in MultiSelect Component" as a bug from our end, and the fix for the issue will be included in our upcoming weekly release which is expected to be scheduled on First week of June 2025.
You can now track the status of the feedback through the below link,
Feedback link:https://www.syncfusion.com/feedback/67732/request-is-not-send-based-on-the-query-take-value-all-the-time-in-multiselect
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,
Priyanka K
Hi Francisco Fernandes,
We would like to inform you that we have resolved the reported issue "Request is not send based on the query take value all the time in MultiSelect Component" in our latest version 30.1.40. Therefore, we recommend that you update your package to the latest version to resolve the current problem.
Release notes: https://blazor.syncfusion.com/documentation/release-notes/30.1.40?type=all#multiselect
Root cause: When we received additional data, we did not account for the value of the Query property, which caused the user-provided take value to function incorrectly.
Regards,
Priyanka K