Hi,
I was wondering if anyone had any suggestions as to the cause of an issue we're experiencing with the radgrid under the following scenario. A user enters filters for grid and the grid updates to reflect the data based on the grid. Everything works like it should so far. If the user clicks on the edit icon for an Item in the grid, then the user is taken to the correct editing page for that Item. Again, everything working properly. The issue is that if the user has filtered on the grid and leaves the page open for a while (e.g., 15-20 min) then when they click on the edit icon to edit an Item they are taken to the Item that would have been the first one listed in the grid if there were no filters (instead of the actual Item they had clicked on).
For example, lets say I have a grid that contains the names Andy, Bob, and Joe, and by default all the names are shown. If I filter on the name 'Bob' then the grid updates to show only that row, and if I click on the edit icon for that row I'm taken to an editing page for Bob's data. All of that works as expected.
However, given the same scenario, if I were to leave the page inactive for a while and then click on the edit icon for the single row in the grid then I'm taken to the editing page for Andy which is what would've been the first row had I not filtered on the grid.
The issue causes problems because our users think they're editing an Item that they filtered on when in actuality they're editing the wrong Item (which is whatever would be the first Item in their default grid with no filtering.
Hopefully my example makes sense!
I was wondering if anyone had any suggestions as to the cause of an issue we're experiencing with the radgrid under the following scenario. A user enters filters for grid and the grid updates to reflect the data based on the grid. Everything works like it should so far. If the user clicks on the edit icon for an Item in the grid, then the user is taken to the correct editing page for that Item. Again, everything working properly. The issue is that if the user has filtered on the grid and leaves the page open for a while (e.g., 15-20 min) then when they click on the edit icon to edit an Item they are taken to the Item that would have been the first one listed in the grid if there were no filters (instead of the actual Item they had clicked on).
For example, lets say I have a grid that contains the names Andy, Bob, and Joe, and by default all the names are shown. If I filter on the name 'Bob' then the grid updates to show only that row, and if I click on the edit icon for that row I'm taken to an editing page for Bob's data. All of that works as expected.
However, given the same scenario, if I were to leave the page inactive for a while and then click on the edit icon for the single row in the grid then I'm taken to the editing page for Andy which is what would've been the first row had I not filtered on the grid.
The issue causes problems because our users think they're editing an Item that they filtered on when in actuality they're editing the wrong Item (which is whatever would be the first Item in their default grid with no filtering.
Hopefully my example makes sense!
3 Answers, 1 is accepted
0
Hello Amy,
The behavior that you are describing could be related to the IIS Idle Timeout (which by default should be 20 minutes) or to the Session Timeout. If a user is inactive for 20 minutes.
Since this is not related to our controls and such behavior could be replicated with any other control, I could only suggest that you take a look at the following articles and forum threads and see if they could help for handling this (by informing the user for the expired session, redirecting to another page or preventing the editing and reload the page):
Hope this helps.
Regards,
Konstantin Dikov
Telerik
The behavior that you are describing could be related to the IIS Idle Timeout (which by default should be 20 minutes) or to the Session Timeout. If a user is inactive for 20 minutes.
Since this is not related to our controls and such behavior could be replicated with any other control, I could only suggest that you take a look at the following articles and forum threads and see if they could help for handling this (by informing the user for the expired session, redirecting to another page or preventing the editing and reload the page):
- IIS: Idle Timeout vs Recycle
- What is the different between Session Timeout and Idle Timeout in IIS?
- Configure Idle Time-out Settings for an Application Pool (IIS 7)
- What is default session timeout in ASP.NET?
Hope this helps.
Regards,
Konstantin Dikov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Amy
Top achievements
Rank 1
Rank 1
answered on 04 Sep 2014, 03:47 PM
Hi,
I don't think it's related to a time-out issue as we have logic to catch that scenario. We present the user with a message indicating their session has timed out and take them back to the login page for the website.
In the scenario I described, the user doesn't get logged out, but is taken to the wrong page for the Item s/he selected from the grid on the previous page (and can continue working in the website). It's as if the user had never filtered on the grid because it seems the filters are being ignored. I don't know the exact amount of time that the page is left inactive and I can't reproduce it on demand (but have it experienced it myself as well); although, I'm guessing it must be at least 5-10 minutes of inactivity.
We use the GridSettingsCollection to store information about the grid which is then serialized and stored in the viewstate. Do you think it's possible the viewstate is becoming corrupted?
Thank you again for your help!
I don't think it's related to a time-out issue as we have logic to catch that scenario. We present the user with a message indicating their session has timed out and take them back to the login page for the website.
In the scenario I described, the user doesn't get logged out, but is taken to the wrong page for the Item s/he selected from the grid on the previous page (and can continue working in the website). It's as if the user had never filtered on the grid because it seems the filters are being ignored. I don't know the exact amount of time that the page is left inactive and I can't reproduce it on demand (but have it experienced it myself as well); although, I'm guessing it must be at least 5-10 minutes of inactivity.
We use the GridSettingsCollection to store information about the grid which is then serialized and stored in the viewstate. Do you think it's possible the viewstate is becoming corrupted?
Thank you again for your help!
0
Hello Amy,
With the provided information only it would be really difficult to pinpoint the exact cause of this behavior.
May I ask you to open a regular support ticket and isolate the problem in a sample, runnable project replicating the same behavior. Thus will allow us to investigate the exact scenario and hopefully, locate the root of the problem.
Regards,
Konstantin Dikov
Telerik
With the provided information only it would be really difficult to pinpoint the exact cause of this behavior.
May I ask you to open a regular support ticket and isolate the problem in a sample, runnable project replicating the same behavior. Thus will allow us to investigate the exact scenario and hopefully, locate the root of the problem.
Regards,
Konstantin Dikov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.