I had to build a new store, build a new model, and then call

grid.setModel(newmodel);
grid.update();

There are plenty of problems with doing it that way, but it works.

-Jon

thanks for the pointer Maine!

I've got the queries happening, and the model store is changing as the server data changes, but the grid isn't updating it's rows to reflect the models changes. I think I'm missing a step here somewhere. I thought the notification api would handle that part?

Thanks for your help, it's gotten me much much closer with much less work...:)

[EDIT]

Found it! Instead of calling the model.store.fetch(), I'm calling model.requestRows(), when I want to update the grid, and it all works beautifully!

Thanks again for the pointer Maine!

-Jon

Any possibility of having an example of this (with enough source to help us newbies) posted?

Thanks in advance,

Shawn

Update the Full grid on the FLY:
retrieve the JSON data "value" from server and extract
var exValue = eval("(" + value + ")");

"model1" is the model you attached with ur grod
model1.setData(exValue);

model1.observer(modelObservers1); // "modelObservers1" is the observer attached to ur model, this is optional

"grid1" is the grid instance
grid1.setModel(model1);

thats all :-)

So, I am doing what you guys are doing above, with the grid.setModel(model) but there's no callback. The data fetching is async, so it works and gets the new data, however, if I want to put a default sort on the grid, or hide the progress icon and show the grid, or whatever, I don't have a callback in which to do that. I imagine that the grid.update() isn't necessary, because anything right after setModel() is run immediately, even before the data has returned.

model.store.fetch() has the onComplete callback, but I've found that it doesn't update the grid successfully in 1.0.2 release or in trunk as of a few days ago. setModel() is the only thing I've found to work.

:(

ideas?

Actually the approach you are trying is simple and correct. If you are getting "..." in your cells that means you need you do some correction in the data format you get from servlet.
Let me explain you somthing Grid is compatible for TWO Dimational or Tabular Data structure.
so if you have somthing like this in grid
111 Name1 Age1
222 Name2 Age2

In that case your JSON value from the server should be like this
[["111","Name1","Age1"],["222","Name2","Age2"],["333","Name3","Age3"]] Array contains Array

I am sure you wont forget to eplod JSON using "eval" methos, before setting data in model ie :
var exValue = eval("(" + value + ")");
model.setData(exValue);

It also has a Callback facility if you have set observer to your model.

Thanks
Manjul

I've given up temporarily on trying to use a model without a store, and recreating ItemFileReadStore and DojoData, as was suggested above. I want to do all sorting on the client without a trip to the server, and the list of data returned will be limited by other form parameters (so I don't want to use QueryReadStore, especially with the luck I'm having on trying simpler approaches).

I can get it to generate a get, but nothing displays. I'm not sure newModel.setData(newStore) is the right thing to do, but I couldn't set newStore with the "store" attribute of DojoData (always got null for the store from the model afterwards). Following is the code:

var userGrid = dijit.byId("userGrid");
        var newStore = new dojo.data.ItemFileReadStore(
                          {url: 'servlet/UserList'});
        var newModel = new dojox.grid.data.DojoData(
                          { rowsPerPage: "20",
                            query: "{ login: '*' }" });
        newModel.setData(newStore);
        userGrid.setModel(newModel);
        userGrid.update();

I was so pleased that the update fix for ItemFileReadStore worked for one of my forms that I forgot why I needed the storeless model. I have another form where the data returned depends on a number of form parameters, in which case the storeless model would be ideal. Since the storeless model works for the above poster, my only guess is that my use of the default model for the grid is causing problems. Declaring the model in the page as I do above gives a null store error when I try to do setData, however.

Well, I feel dumb, but am posting this in case someone else makes the same mistake. In the view, I left in the fields attribute of the cells from when I was using a store. I took those out, and things work fine. Apologies for the wasted bandwidth.

Is there a way anymore to populate a grid analogous to the following simple manner:

var resvGrid = dijit.byId("resvGrid");
var model = resvGrid.model;

// resvData is a list of lists from the server
oscars.Reservations.convertReservationTimes(responseObject.resvData);
// is there some way to get the data into the grid now that there is no model
model.setData(responseObject.resvData);
resvGrid.update();

My entire application is built on doing things this way. I've looked at the source, including _Grid.js, and the tests, and don't see the way to do it.

I've seen this question all over the forums, so I'm posting this answer in a few different places. I had this same question and couldn't find an easy solution right away. After playing with it for a bit, I finally remembered the dojo.data api call for the "close()" method.

Using a Dojo 1.2 DataGrid widget that is loaded via a URL with ItemFile****Store (Read/Write), the Grid can be refreshed (using the same URL) with a few simple commands, without having to replace the datastore.

First, create the Datastore with the "clearOnClose" parameter set to true:

	var myDatastore = new dojo.data.ItemFileReadStore( { url: "myUrl.json", clearOnClose: true  } );

Then, create your DataGrid (e.g. "myGrid") with whatever setup you need. When you want to reload the data, have your button (or whatever) execute the following:

	// Close the datastore and tell the DataGrid to refresh.
	myGrid.store.close();
	myGrid.sort();

The sort function internally forces a refresh, and that's what will cause the grid to fetch the data from the datastore again. Since the datastore has been closed (and cleared because of the "clearOnClose" property), the data will be requested from the URL again.

This isn't a complete example. The details of creating the DataGrid widget are left out, since there are many ways to do it, depending on the situation.

Cheers,
~Michael

Has anyone found a best practice/method for updating/refreshing a grid without getting the "Loading..." screen? I'm currently polling a cgi script that outputs changing JSON data every 2seconds (I eventually want to migrate to a comet type solution). What I'm trying to get is the look and feel as when I delete a row with: store.deleteItem(selectedItem); where the row is immediately deleted. Is there a practice to get the grid to update instantly, much like on an item deletion?

I'm sorry if this has already been asked, but I've been searching documents and forums for the last couple mornings. Thank you.

To help others who might come across these issues, here's what I've found about forcing a QueryReadStore to re-request the data from the store. This is with version 1.3.0. QueryReadStore, keeps a copy of the last request it has sent to the server. It compares the new request to the old request to determine if it can use a cached copy of the data. This is great if you want caching. However if your application is aware that data on the server has changed, there are only two choices that I've found to work for forcing a refresh.

1. create a complete new QueryReadStore object and tell your grid, tree, etc. to use it.

I think this is considered the preferred way. However, if you are creating your store in markup as many examples show, you need to change over to creating it programmatically.

2. set storename._lastServerRequest to null.

_lastServerRequest has the a copy of the request parameters as a json object. It is a private member, is likely to change and therefore shouldn't be counted on. However if you are creating your store from markup it works.

QueryReadStore's implementation of close is a no-op. I think that is wrong. If it's not going to do anything I think it should throw an unimplemented exception, rather than just silently doing nothing.

What I've done is to override the close method and make it set _lastServerRequest to null.

Once this is done a call to gridname.sort() will cause a fetch and a grid refesh.

Hope this helps someone,
--Rob