DataGrid grouping example confusing about blazorise HOT 5 CLOSED

When you sort on the gender only one gender-group is displayed.

I was just testing this. Yea I was confused at first also. The thing is, only 10 records are displayed at a time from a total of like 500.

If you order by Gender, well you get only the first gender records, so other buckets do not show as there's no records for the other buckets in this page. This seems correct, but maybe a little confusing indeed.

We can indeed change the example to just handle like a few records which should be more clear. But I'm thinking if we should do anything else here to be more clear when there's alot of records?

@stsrki any thoughts?

from blazorise.

If you use ReadData mode, then this is how it behaves, as we don't see all the records. With ReadData, the developer is responsible for the proper fetching and grouping of data.

On the other hand, if this is in memory, then it is definitely wrong.

from blazorise.

If you use ReadData mode, then this is how it behaves, as we don't see all the records. With ReadData, the developer is responsible for the proper fetching and grouping of data.

On the other hand, if this is in memory, then it is definitely wrong.

It's our docs:
https://blazorise.com/docs/extensions/datagrid/features/grouping

Why do you say it's definitely wrong? Are you jumping the gun? Did you understand the "issue" 100%?

If you order by gender which is the column the data is being grouped on.
Since we all alot of data, the the first 10 records will certainly only belong to a single bucket, so only a single bucket (group) shows.

If you say it's definetly wrong, what do you think should happen?

• All buckets show? But other buckets are empty?
• Not able to order at all by that column, since it's the column the data is grouped on?
  • Nah I don't think this even makes sense.

from blazorise.

I see now. Didn't understand that problem is on our demo.

It seems like a bug, indeed. Would it help if we enabled pagination? That way users would see that there is more data available.

from blazorise.

I see now. Didn't understand that problem is on our demo.

It seems like a bug, indeed. Would it help if we enabled pagination? That way users would see that there is more data available.

Right It seems like a bug, but I am thinking that's it. It just seems like it.
Either we reduce the amount of data so it's clearer. Or allow pagination like you just suggested, that might be indeed a bit clearer.

from blazorise.