Latest Contributions by MatthewTownsend

After talking with ESRI support we modified the Query Widget Javascript slightly to get it working. The problem is that if it has a joined view it returns an empty feature list for the results of an object ID query. Basically I modified it to always do the backup query using the objectID field name (in my case SDEADMIN.ServicePointBank.ObjectID).  The issue in this case was that the feature with the view joined to it was NOT getting an error.  Instead it was returning "successfully" with a count of 1 but an empty feature collection.  The downside to the change below is that for multiple results you will more quickly run into the max URI length.  Seems to me that the best option would be to just get the feature result from the original query (in my case SPID = 'some number') rather than getting the object IDs from that query and then querying again using the object IDs as the Widget is currently setup to do.  For now, this change will do. Old code from Query/SingleTask.js: _queryByObjectIds: function(objectIds, returnGeometry){         var def = new Deferred();         var queryParams = new EsriQuery();         queryParams.returnGeometry = !!returnGeometry;         queryParams.outSpatialReference = this.map.spatialReference;         queryParams.outFields = this._getOutputFields();         queryParams.objectIds = objectIds;         var queryTask = new QueryTask(this.currentAttrs.config.url);         queryTask.execute(queryParams).then(lang.hitch(this, function(response){           def.resolve(response);         }), lang.hitch(this, function(err){           if(err.code === 400){             //the query fails maybe becasuse the layer is a joined layer             //joined layer:             //http://csc-wade7d:6080/arcgis/rest/services/Cases/ParcelWithJoin/MapServer/0             //joined layer doesn't support query by objectIds direcly, so if the layer is joined,             //it will go into errorCallback of queryTask.             //the alternative is using where to re-query.             var objectIdField = this._getObjectIdField();             var where = "";             var count = objectIds.length;             array.forEach(objectIds, lang.hitch(this, function(objectId, i){               where += objectIdField + " = " + objectId;               if(i !== count - 1){                 where += " OR ";               }             }));             this._query(where, null, returnGeometry).then(lang.hitch(this, function(response){               def.resolve(response);             }), lang.hitch(this, function(err){               def.reject(err);             }));           }else{             def.reject(err);           }         }));         return def;       }, New Code: _queryByObjectIds: function(objectIds, returnGeometry){         var def = new Deferred();         var queryParams = new EsriQuery();         queryParams.returnGeometry = !!returnGeometry;         queryParams.outSpatialReference = this.map.spatialReference;         queryParams.outFields = this._getOutputFields();         var where = "";         var objectIdField = this._getObjectIdField();         var length = objectIds.length;         array.forEach(objectIds, lang.hitch(this, function (objectId, i) {             where += objectIdField + " = " + objectId;             if (i !== length - 1) {                 where += " OR ";             }         }));         queryParams.where = where;         var queryTask = new QueryTask(this.currentAttrs.config.url);         queryTask.execute(queryParams).then(lang.hitch(this, function(response){           def.resolve(response);         }), lang.hitch(this, function(err){ def.reject(err); }));         return def;       }, ... View more

I voted for the idea you posted above... We eventually opened up an incident with ESRI.  They told us that the ability to custom name the views is no longer available.  They told us that we could point a 10.0 SP4 SDE Application Service (what we were running before) at the 10.2.1 database and use it to rename.  I haven't tried it yet.  Eventually we will just have to use their standard naming so we are working toward that. ... View more