Latest Contributions by derekswingley1

Good to know you're using a dynamic layer. You don't need to wait for the map to load to add the layer to your map. Do you see a request for <Nielsen Layer URL>/export when your app loads? How long does that request take to complete? You can check this in Chrome or Firefox's dev tools. Or with a tool like fiddler. ... View more

Is the layer that's not displaying an ONDEMAND mode feature layer? Try adding your layer after the map's onLoad event fires. This is shown in the "On Demand Mode" Feature Layer sample. ... View more

I think your latest testing points to an issue with your web server. Again, I would check that your IIS instance is configured to serve JSON. ... View more

What are the specific errors you're seeing? Do you see the same errors when you load the copy of the sample we host:  http://help.arcgis.com/en/webapi/javascript/arcgis/demos/layers/layers_point_clustering.html ... View more

Glad to help. Attached is what I see when I used enable-cors.org to check if CORS is supported on services.arcgisonline.com. That server is not set up for CORS. ... View more

Have you tried using ONDEMAND mode? Even though you only have 17 records, you're using polygons and I'm guessing those are pretty detailed geometries. Loading a couple of MB of geometry would be plenty to cause what you're describing in IE. Since you're using 2.8, ONDEMAND mode will generalize features on the fly for the map's current zoom level and feature geometry will be updated as the map zoom level changes. SNAPSHOT mode does not do this and retrieves each feature's full geometry. Using ONDEMAND, you should see a performance improvement in all browsers, not just IE. ... View more

Hi John, You can safely ignore these errors. There's info about this in the doc for esri.request (specifically, the bullet for 3.0). Kelly also posted about this a couple of days ago:  http://forums.arcgis.com/threads/59988-Issue-Upgrading-to-version-3.0?p=207055&viewfull=1#post207055 ... View more

As an addendum, this in fact causes faulty behavior if, as in that sample, the next feature you mouse-over features a value of 0 for some of its data--the corresponding gauge will remain filled in to whatever value you manually input by clicking on the gauge. It's a bug. We'll fix this in the next release. ... View more

The data used for clustering is in a .json file. Is your IIS instance configured to serve JSON? ... View more

On Bing maps I just confirmed that MAP_STYLE_AERIAL_WITH_LABELS is what doesn't print vs your version of MAP_STYLE_AERIAL.  Strangely similar to the textsymbol bug. Thanks. Also a bug...the print dijit is sending the wrong layer.type property to the print service. It is sending "BingMapsaerialWithLabels" instead of "BingMapsHybrid". Here's a workaround:  http://jsfiddle.net/axPwz/ The key is using esri.setRequestPreCallback to update the JSON that's sent to the print service. Here's the relevant code: function fixBingHybrid(ioArgs) {   // look for requests to the print service   if ( ioArgs.url == app.printUrl + "/execute" ) {     var webmapJson = dojo.fromJson(ioArgs.content.Web_Map_as_JSON);     // check that the webmap JSON has operational layers     // bing is always considered an operational layer     if ( webmapJson.operationalLayers.length ) {       dojo.forEach(webmapJson.operationalLayers, function(lyr) {         // correct the type property for the bing hybrid layer         if ( lyr.type && lyr.type == "BingMapsaerialWithLabels" ) {           lyr.type = "BingMapsHybrid";         }       });       ioArgs.content.Web_Map_as_JSON = dojo.toJson(webmapJson);     }   }   return ioArgs; } And this line in the init function: esri.setRequestPreCallback(fixBingHybrid); ... View more

Thanks. Looks like the text symbol issue is a bug. I'll post a bug ID to track it once I've confirmed. I see bing maps in the print output here:  http://jsfiddle.net/zKaVn/ ... View more