Hi,
New to Ignite grid. We implemented that grid in MVC . We need to get the Last Clicked column in Grid.
Requirement 1.
We add Load more button if user click the Load more button we passed last Clicked sorted column and loaded in Grid again based on that Sorting to maintain.
Requirement 2:
Lazy loading in that grid if user scroll last window we pass the value and load some more data .Here also sorting needed.
Kannan.
Hello Kannan,
Thank you for posting in our forums!
Could you please clarify the issue for me by answering the following questions?
1.) Does the grid not automatically maintain the expected sorting when loading new rows?
2.) What version and build of IgniteUI are you experiencing this with? e.g. 14.1.20141.2249
3.) Are you using remote or local sorting?
4.) For requirement 1, are you saying you are storing the sorted column details and reapplying the sorting after the "Load more" button is clicked?
5.) For requirement 2, are you saying that the same sorting issue occurs when using loadTrigger: "auto" for the Load on Demand feature?
Looking forward to hearing from you.
Thanks for the mail . I wounder that Grid maintain the same sorting While loading again. We have the license for 12 .2 ...
Req 1: We fetch the data ( 10 Records ) from DB and load grid . When user clicks the Load more button again we fetch 10 more data add it grid ( old data maintain in session)
Req 2:The same concept we try to implement Lazy loading.
Project flow : Button click - Ajax json - DB call- bind
we use sorting type is "local" .But still am not Clear about diff b/w local and Remote.
If you are proving any sample it will be helpful
Can you provide sample Link.
Hi Kannan,
I am currently researching and putting together a sample that demonstrates these behaviors for you.
I will have another update on my progress for you tomorrow.
I will need some more time to finish putting my sample together. I currently have load on demand working with sorting when sorting is set to remote.
For more information on the differences between local and remote sorting, please see our documentation here:
https://www.igniteui.com/help/14.1/iggrid-sorting-overview
This documentation describes local vs. remote sorting as such:
Sorting can be configured to operate either locally or remotely. In the first case, sorting is done entirely on the client, without the need of any server requests. In the case of remote sorting, the grid encodes the necessary URL parameters so the server can retrieve information about which columns must be sorted.
I have attached my current MVC sample that shows how you can set up Load On Demand and sorting on the igGrid. In my sample I have Sorting set to remote. This means that when sorting a column, the results will be obtained from the server. You will notice a request sent to the server when sorting a column. This allows the sorting to remain consistent when loading more data.
When I have Sorting set to local in my sample, I do see the behavior you are describing where the newly loaded rows are added to the grid without being properly sorted. I am bringing this up with our developers and I will need a little more time to get this together for them.
I will have an update on this for you tomorrow and continue working on my sample to implement lazy loading for this.