Latest Contributions by BenFousek

Okay the fiddle helps: function populateGrid(Memory) {   //populate grid code here   //now listen for the feature layer update   fl.on('update', function () {     var qt = new QueryTask(window.unitsUrl);     var query = new Query();     query.where = "1=1";     query.returnGeometry = false;     query.outFields = window.outFields;     qt.execute(query, function (results) {       var data = [];       var data = array.map(results.features, function (feature) {         return {           // property names used here match those used when creating the dgrid                            "id": feature.attributes[window.outFields[0]],           "vehicleId": feature.attributes[window.outFields[1]],           "velocity": feature.attributes[window.outFields[2]],           "timestamp": feature.attributes[window.outFields[3]]         }       });     });     window.grid.setStore(new Memory({       data: data     }));   }); } Something else you might look into is the feature layer's 'update-end' event and use the features of the feature layer directly to avoid extra requests to the server. ... View more

The gird is independent of the layer updating. You need to use an event to listen for the update of the feature layer and update the grid. Not knowing exactly how your app is setup, but assuming your layer is called "layer": layer.on('update', function () {   var qt = new QueryTask(window.unitsUrl);   var query = new Query();   query.where = "1=1";   query.returnGeometry = false;   query.outFields = window.outFields;   qt.execute(query, function (results) {     var data = [];     var data = array.map(results.features, function (feature) {       return {         // property names used here match those used when creating the dgrid                          "id": feature.attributes[window.outFields[0]],         "vehicleId": feature.attributes[window.outFields[1]],         "velocity": feature.attributes[window.outFields[2]],         "timestamp": feature.attributes[window.outFields[3]]       }     });   });   window.grid.setStore(new Memory({     data: data   })); }); Just a simple example, but hopefully gets you going in the right direction. ... View more

I looked at a couple of my grids and I simply create a new store and set it. ... View more

When your new data is returned, create a new store and set the grid's store to the new store. Or just reuse your store and reset its data. As I recall this should update the grid. ... View more

Thanks Jon, I missed that part. I guess when I look at the return I expect to see everything I'm getting. Here's another for you. https://developers.arcgis.com/javascript/jsapi/featurelayer-amd.html#queryfeatures In the sample it shows "esri/tasks/Query" instead of esri/tasks/query". ... View more

Here's some follow up for interested parties. Until yesterday I'd never really used PrintTask or associated classes, instead creating my own Web_Map_as_JSON and making a independent request for a couple reasons: 1) I didn't want to print all layers, e.g. a results layer or custom gp layer. 2) Sending attribute and info template json can exponentially increase the size of the request and with no benefit. And cause errors, especially with text symbols. This approach has worked well, but has required a lot more coding and code maintenance as dojo/jsapi have evolved. Wanting to reduce code and let the native esri classes do the heavy lifting, this is my 26 lines of code to get the same result. With the following understanding: 1) layers that are not to be printed are extended with layer._print = false;, 2) this example is out of a custom class (hence the hitching), and 3) this.map is in fact the map. esriRequest.setRequestPreCallback(lang.hitch(this, function (args) {     //Web_Map_as_JSON to js obj     var json = JSON.parse(args.content.Web_Map_as_JSON);     //remove map.graphics     json.operationalLayers.splice(arrayUtils.indexOf(json.operationalLayers, this.map.graphics.id), 1);     //remove non-print layers     arrayUtils.forEach(json.operationalLayers, function (ol) {         var layer = this.map.getLayer(ol.id);         if (layer._print && layer._print === false) {             json.operationalLayers.splice(arrayUtils.indexOf(json.operationalLayers, ol), 1);         }     }, this);     //strip graphic layer attributes and and info templates     arrayUtils.forEach(json.operationalLayers, function (ol) {         if (ol.featureCollection && ol.featureCollection.layers.length) {             arrayUtils.forEach(ol.featureCollection.layers, function (layer) {                 arrayUtils.forEach(layer.featureSet.features, function (feature) {                     if (feature.attributes) {                         delete feature.attributes;                     }                     if (feature.infoTemplate) {                         delete feature.infoTemplate;                     }                 });             });         }     });     //json to Web_Map_as_JSON     args.content.Web_Map_as_JSON = JSON.stringify(json);     return args; })); A final consideration. If you are using a custom print task server side and need attributes to do something cool, like create a table of attributes for a selected feature or label graphics, then steps would need to be taken not to strip those attributes from those layers. ... View more

Thanks Jon, I'm aware of dgird's styling. Can't seem to find any examples of content fitting. I'll hit up dojo for an answer too. Ben ... View more