Latest Contributions by ReneRubalcava

So I ran into this problem with (version 3.9) esri/arcgis/utils#createMap where my defined basemap layer is down, so the map creation errors out completely and breaks my app. arcgisUtils.createMap(webmapJSON, elementId, options).then(onSuccess, onError); What I can do is use the error function to add a different basemapLayer url (like the Esri World Imagery), but there are a few issues here. Error seems to delete basemap object from basemapLayers array: This means I have to add a new object instead of just change the URL. It would be cool if you didn't mutate my objects. Error only tells me a URL is not valid: This could mean it's a basemapLayer or maybe an operationalLayer (map fails to create with a bad op layer URL too, checked), I'm not sure how to tell. This makes error handling these kind of things more difficult. Map creation doesn't need to be halted because of a bad URL: A map can exist without a basemap, maybe add the errors to the response callback to check for any errors that occured during the map creation process. In this case, I can tell after the fact that the basemapLayer is dead, but this doesn't help me in production to handle these errors if I can't tell what has gone wrong. The Error codes do contain an empty details array, so maybe the JS API internals could populate that with some more useful information. Although I like the idea of not breaking map creation because of a bad URL to begin with. It's much easier to handle a missing layer inside the application than it is to decipher what went wrong in the map creation process. *edit* - I just double-checked. The response object from the createMap promise does have an errors array. Can you just put any map creation errors there, including invalid URL errors? I suppose I'm confused why a broken basemap/operational URL will halt the map creation process. ... View more

So I have a few FeatureLayers in selection mode. They all share a common field, let's say "FEATURE_ID". One of the layers also has a field called "MAIN_FEATURE_ID". So I give a query like so.       var q = new Query();       q.where = "FEATURE_ID = '" + featureid +         "' OR MAIN_FEATURE_ID = '" + featureid + "'"; Now, I know that query is going to error out on 2 of my 3 FeatureLayers because only 1 has that second field. I don't care, that's what the error handler callbacks are for. So I do something like this for my FeatureLayers       var queries = arrayUtils.map(this.get('featureLayers'), function(lyr) {         return lyr.selectFeatures(q, FeatureLayer.SELECTION_NEW);       }, this); Then I use dojo/promise/all to get all the data when everything is done.       all(queries).then(lang.hitch(this, function(results) {         var data = [];         data = data.concat.apply(data, results);         if (merged.length) {           this.get('map').setExtent(graphicsUtils.graphicsExtent(merged));         }       }), function(err) { // capture the errors here         console.debug('error', err);       }); What is happening here is that my error prints to console, but the API is throwing an internal error Error {code: 400, message: "Unable to complete operation.", details: Array[0], log: undefined, httpCode: 400???} init.js:187 This breaks something because not my success function doesn't get called either. If I check the network trace in Chrome dev tools, I can see the queries and responses, 2 of the requests return an error code of 400, but the last one returns valid results, but something is blocking that result from bubbling up to my success call. If I change the query to only search the one common field, everything is fine. Any clues? I tried adding my own Deferred and returning the Deferred#promise and capturing the error, thinking maybe there was a quirk in dojo/promise/all       var queries = arrayUtils.map(this.get('featureLayers'), function(lyr) {         var def = new Deferred();         lyr.selectFeatures(q, FeatureLayer.SELECTION_NEW).then(function(response) {           def.resolve(response);         }, function(err) {           console.debug('query error', err);           def.resolve([]);         });         return def.promise;       }, this); Still no good. It looks like the errors the API throws are killing my success function. I know I'm going to get errors, I'll deal with it, but is this the intended behavior? Thanks. ... View more