Hi,
Below is the code for my paging, features.Paging().PageSize(10).Type(OpType.Local).PageCountLimit(100).ShowPageSizeDropDown(true).ShowPagerRecordsLabel(true).PrevPageLabelText("Prev").RecordCountKey("totalRecords");by default the page column size is set to 10, but if i enter 11th value, it moves to next page as expected but as i enter the new value after grid refreshing it show page 2 instead of page 1, the new value is on page 1
Hello Azhar,
Thank you for posting into our community!
I have been looking into your question, however, I will need some additional information regarding your scenario in order to ensure that your question is addressed correctly.
You have mentioned that after you “enter the new value after grid refreshing it show page 2 instead of page 1”.
Could you please clarify what do you refer to with “after grid refreshing”? Do you mean after navigating to a different page or after changing the page size from the drop down?
Additionally, by "show page 2 instead of page 1", do you mean, for example, after changing the page size the shown page is 2?
Answering these questions would be highly appreciated and extremely helpful in providing you with a solution as soon as possible. Also, it would be great if you could provide me with a small and isolated sample that demonstrates the behavior on your side and elaborate on the steps to reproduce it?
Having a sample which I can debug on my side will be extremely helpful in investigating the root cause of this behavior.
Thank you for your cooperation. Looking forward to your reply.
Sincerely,Riva IvanovaEntry Level Software Developer
I have a "date" type igx column in my snake game website. These columns contain string values. Following the convention of "DD.MM.YYYY," the date is shown. Can the yyyy-mm-dd date format in the igx column be changed without affecting the string itself?
Hello,
I have been looking into your question and I am under the impression that you are using the Ignite UI for Angular controls?
Having this in mind what I would suggest is creating a separate thread in the Ignite UI for Angular section here as the current thread is regarding Ignite UI for ASP.NET Core paging functionality.
This is for better consistency and history tracking.