The whole point of EnableVirtualization is to only render a subset of data (resulting in reduced HTML content). When using remote data to populate a virtualized SFDropDownList it also stands to reason that the Read/ReadAsync DataManagerRequest should also be requesting a subset (e.g. DataManagerRequest Take value should be some small finite number). This works as expected for a SFGrid (e.g. Skip=16,Take=8) but for a SFDropDownList the initial and only DataManagerRequest has a Skip=0 and Take=0. In Syncfusion 19.4.0.56 this initial request was fired but then there was also a subsequent request for a larger Take value (equivalent to the SFDropDownList.ItemsCount value). Now in Syncfusion 20.2.0.36 however only the initial Take=0 request exists and of course the outcome will be a list that results in 'No Records Found'. The initial Take=0 request in 19.4.0.56 seemed redundant especially given that it also wasn't requesting for the DataManagerRequest.RequiresCounts value (which the native Blazor Virtualize component uses to determine scroll bar size) but nevertheless, at least it then requested more data. To expect that a DataManagerRequest.Take=0 responds with the entire DataSource is naive and can never work for an infinite remote data set.
It was also noticed in 19.4.0.56 that subsequent ReadAsync calls always had a Skip=0 value which we figured was a defect and assume has since been fixed as part of another issue we saw on this forum.
Hi Harryi,
We have validated the reported query on our end. Unfortunately, we couldn’t reproduce the reported issue as per your scenario. Also, we request you to provide additional details about the issue as mentioned below, This will help us validate the issue further and provide you with a better solution.
Are you facing the issue in any particular scenario?
Is the DropDownList component rendered within any other component or alone?
Issue replication sample (or modify the attached sample).
Issue replication steps.
Video illustration of the issue.
Regards,
Udhaya Kumar D
Hi,
Thank you for your response. In Syncfusion 20 it appears a Query object with a Take value is now required to seed the DataManager request. This wasn't required in Syncfusion 19. We have no problem in specifying this.
Thank you.
Hi Harryi,
Thanks for the update. Please get back to us if you need any further assistance.
Regards,
Udhaya Kumar D