Latest Contributions by JoelBennett

I haven't yet transitioned to ESM modules, so don't have an answer for you.   However, you might check out this post, which discusses updating Popup style via JavaScript. ... View more

Perhaps it's related to the issue described in this post. ... View more

If you're just wanting to show a particular set of features at any given time, and know the objectID values of that set, then using definitionExpression would be one way to do so: function hideLayerFeatures(featureLayer) { featureLayer.definitionExpression = "1=0"; } function showLayerFeatures(featureLayer, ids) { if (Array.isArray(ids)) featureLayer.definitionExpression = featureLayer.objectIdField + " IN(" + ids.join(",") + ")"; else if (typeof ids == "number") featureLayer.definitionExpression = featureLayer.objectIdField + " = " + ids.toString(); } ... View more

If you examine the contents of the request to generate the printout, does it appear to be sending the graphics (i.e from app.theView.graphics) as JSON, or is it sending a screenshot of them?  It seems to me this problem could occur if it's doing the latter. ... View more

This "should" be handled by the scalePreserved property of the PrintTemplate, in which case line 44 of your 4.x code should probably be set to true. ... View more

This is an old thread, but it's still Google's first result for "arcgis server stops immediately", so I ended up here today.  In our case, if we started the ArcGIS Server service from the Windows services console, it would act as if it started, and its status would be "Running".  However, clicking refresh immediately after would show it was no longer running. There was nothing useful in the Event Viewer, and the only indication anything was happening at all was the creation of an empty log file in C:\Program Files\ArcGIS\Server\usr\logs\[server_name]\server. To make a long story short, this one turned out to be a file system permissions issue.  We use a domain account to run the service, and among other things, it's granted certain permissions on the "arcgisserver" folder.  Evidently, somebody inadvertently removed that account's permissions and this situation was the result.  After adding the permissions back, the service is operating normally. ... View more

Thank you @KristianEkenes, I didn't know about queryAggregates, but it's a game-changer for this problem.  However, there are a couple subtleties about this approach that have to be taken into account, one of which I think should be classified as a bug. I've revised my "checkCluster" function below, which produces accurate results now:   function checkCluster(view, graphic) { return new Promise(function(resolve, reject) { view.whenLayerView(graphic.layer).then(function(layerView) { layerView.queryAggregates().then(function(featureSet) { var aggregateIDs = []; featureSet.features.forEach(function(feature, index) { // if (feature.attributes.cluster_count === 1) // console.warn("Aggregate feature with OID " + feature.getObjectId() + " has cluster count of 1; this shouldn't be possible..."); if ((feature.attributes.cluster_count > 1) && (view.extent.intersects(feature.geometry))) aggregateIDs.push(feature.getObjectId()); }); if (aggregateIDs.length === 0) resolve({graphic:graphic, isCluster:false}); else { var query = layerView.createQuery(); query.aggregateIds = aggregateIDs; layerView.queryFeatures(query).then(function(featureSet2) { for (var x = 0; x < featureSet2.features.length; x++) { if (featureSet2.features[x].getObjectId() == graphic.getObjectId()) { resolve({graphic:graphic, isCluster:true}); return; } } resolve({graphic:graphic, isCluster:false}); }, reject); } }, reject); }, reject); }); }     The two subtleties are addressed on line 11.  One is that queryAggregates, as documented, doesn't support spatial queries.  This is fine in and of itself...just something to be aware of.  The second condition in line 11 is used to filter only results that intersect the View, but that may not be necessary depending on your needs. The other issue is addressed by the first condition, and also further highlighted by lines 8 and 9, which are commented out.  The queryAggregates function can (and does) return features with a cluster_count of 1 (one).  I don't think this should be possible.  Here is a quote from the FeatureReductionCluster documentation (all emphasis is found in the original): "This documentation refers to two kinds of features: aggregate features and individual features. Aggregate features represent clusters. Clusters always represent two or more features. There's no such thing as clusters with a count of one. If a feature does not belong to a cluster, it is considered an individual feature." I don't think the documentation there could really be any clearer.  If "there's no such thing as clusters with a count of one", then I don't think queryAggregates should be returning features with a cluster_count of one.  It definitely threw me for a loop as I was revising my function. ... View more