Just as a note, I have 5 grids on one page in a particluar instance with no issues. When you select a row on the first grid (onSelectRow) it calls the other 4 grids and loads their data. Each one of these grids suports editing and require lookup data (drop downs) in the form edit mode so I get the data within each grids declaration with the jQuery ajax call and am sure to use the
async: false
property, which ensures that each grid is loaded without overlapping sessions or threads.
On another note Darren, I keep the previous value of the number of rows per page on my server (Mvc app) and when it posts back for any reason I check to see if the number of rows per page has chnaged, and if so, send them back to page 1. However, I was using a sessions variable MyjqGridRowsPerPage and since I have many grids on the same page will need to create a different one for every grid, seems like a lot of work, how did you handle this situation with the user changing the number of rows per page? Tony do you have any suggestions?
I wonder about using id's in a case like this at all… seems like the template should never have id's, in the case where I want to reuse the same template on the same page (imagine a desktop with instances of a grid class, all having a template with a repeated id). This won't work, simple DOM rules.
jqGrid is also inserting duplicate id's when two grids are on the same page for me.
I'm very surprised by this, not sure what to think. I've seen it do different things on different days so it could be somewhat dependant on how I have the page organized, but looks like this:
Setting id is recommended for proper work. Also you can generate your own id using random generator. The fasted way to every dom manipulation is to query it by ID.