Thanks for your help so far.

I have attached the document having the snapshot of the grid, which we need to develop usign ASP.NET Ajax Data grid.

Can you please suggest the best approach to code these kind of the grids.

We need it urgently.

Thanks in advance.

Laxmi P

Hi,

Laxmi2012 said:

The checking is done on Server side. Is there a property on server side that can make a cell readonly on the server side code or we will have to pass that information in ajax call back to client and do the formatting.

The server-side of our jQuery controls only handles remote features (currently: group-by, paging, sorting, filtering, updating and summaries).
Some features are client-side only - column resizing, column hiding and selection.
Thus, I'm afraid that we do not provide an out-of-the-box way to manipulate selection based on server-side logic. 
(Side note: Our  ASP.NET grid has selection that can be manipulated by server-side logic; just take a look at this sample: http://samples.infragistics.com/aspnet/Samples/WebDataGrid/EditingAndSelection/SelectionServerEvents/Default.aspx?cn=data-grid&sid=4c7af2f6-e6b4-4301-97ef-d0bac182d9dd)

What I can recommend in order to have server-side-manipulated (allowed/forbidden) selection is to have an event handler for either the cellSelectionChanging or the rowSelectionChanging events.
In that handler you should make an AJAX call to your server-side and based on the outcome, allow the selection to be carried out or to be cancelled (by returning false in end of the handler).

Here are some suggestions on how to perform the AJAX call in this situation:
http://stackoverflow.com/questions/755885/how-do-i-make-jquery-wait-for-an-ajax-call-to-finish-before-it-returns 

Hope this helps.
All the best,
Borislav 

 

Hi Laxmi,

Laxmi2012 said:

1. On one web page maximum how many JQUERY grids can be added to achieve the good page load perfomance. 

The general answer is: "as many as you like", because no one is asking you to initialize all of the grid at the same time, thus if you load grids in batches or only when necessary, you can achieve some pretty good page performance.

Also, each grid can be removed from the page when it's not being used so you can avoid unused grids.

Also, you can take a look at our official performance guide for the igGrid:
http://help.infragistics.com/NetAdvantage/jQuery/2012.1/CLR4.0?page=igGrid_Performance_Guide.html 

Laxmi2012 said:

2.  Is there a way to move client code like setting up features, handling editcellstarted event, etc to move to server side? If so how much benefit can we expect in terms of performance

 
Setting up the UI for the grid's features is very light-weight as it is and cannot be improved by server-side handling.
On the other hand, some features can have server-side implementations instead of client-side - you can take a look at the official igGrid samples - a lot of the samples use remote (server-side) features so you can see what their performance is.

Events are client-side only so if you want them to be handled by a server, you have to write JavaScript event handler functions which make AJAX calls to your server logic - during that time you need to make the grid wait for the server logic to complete.
I don't think that client-side event handling should trouble you - its performance will be near excellent.


If you have any specific concerns or situations that you have doubts about, please let me know so I can give you some specific details. 

Cheers,
Borislav