Latest Contributions by AndrewMurdoch1

Good Day I'm using "@arcgis/core": "4.27.6" I think I found a bug in the querying logic when setting a definition expression (DE).  Assume I have a layer and I set the DE to 'a = 1 OR a =2', and two of the X features are now shown. If I run another query on the map: 'a = 3', and get back a feature / geometry, why is the visible flag still true when the feature isn't visible?  Should I be able to use a DE as a first pass filter that's constant, and then on top of that apply more filters using queries?  This is a code sample of what I'm doing: Definition Expression Stage, assume query: 'a = 1 OR a = 2':     this._view?.map?.layers?.forEach((layer) => { if (layer?.type === 'feature' && !layer?.id.includes('meta-')) { layer.definitionExpression = query; } }     Running the second query, assume mapQuery is: 'a = 3':     const query = { where: mapQuery, outFields: ['*'], returnGeometry: true } const visibleFeatures: Graphic[] = []; this._view.when(() => { this._view.map.layers.forEach((layer) => { if (layer.type === 'feature') { layer.queryFeatures(query).then((queryRes) => { queryRes.features?.forEach((feature) => { if (feature.visible) { visibleFeatures.push(feature); } }) r(visibleFeatures); }).catch((error) => { console.log(error); j(error); }) } }) })       When I look for anything but a 1 or 2, they aren't visible on the map, so that flag shouldn't be set. Thanks ... View more

Good Day I'm not sure the right way to file this issue, but can someone please update the documentation for View / Map Destroy?  https://developers.arcgis.com/javascript/latest/api-reference/esri-views-View.html#destroy Can a statement be added that says something like: “Please note, the service / web workers which are allocated from the map / view, will not be destroyed.  This is intentional and by design <insert reason here>”. I understand that calling view.destroy() and map.destroy() will not release the workers, and that's fine. It would be helpful if the above comment was added into the documentation, because it's not evident from the description, which would imply they should be. “Destroys the view, and any associated resources, including its map, popup and UI elements. These can no longer be used once the view has been destroyed. To prevent these components from being destroyed, remove them from the view before calling destroy().” Thanks ... View more

Good Day I have a weird issue where my PrintTask outputs are missing legend, sometimes, but not others, and I can't find a pattern as to why.  I have a unique value render setting with ~160 different values in it, and on most of the maps I use a valueExpression to set the renderer.  If I take two maps which use the same valueExpression, literally the same one, and compare them, one will generate with legends, and the other won't. Map 1: Map 2:   The valueExpression: When($feature.aType == 3 && $feature.ci > -10 && $feature.ci <= 40, 'condition_3_Crititcal',$feature.aType == 3 && $feature.ci > 40 && $feature.ci <= 50, 'condition_3_Poor',$feature.aType == 3 && $feature.ci > 50 && $feature.ci <= 65, 'condition_3_Fair',$feature.aType == 3 && $feature.ci > 65 && $feature.ci <= 90, 'condition_3_Good',$feature.aType == 3 && $feature.ci > 90 && $feature.ci <= 99, 'condition_3_Excellent',$feature.aType == 3 && $feature.ci > 99 && $feature.ci <= 100, 'condition_3_Perfect',$feature.aType == 3 && $feature.ci > -10 && $feature.ci <= 0, 'condition_3_Not Defined','condition_Not Defined') That is the valueExpression shared by both maps, the first will generate a legend, the second won't.  This is my print function:   public printMap(): void { const titleText = 'Map: '; /* let layerLegend = new LegendLayer(); let layerIds = []; this._view.map.layers.forEach((layer) => { layerIds.push(layer.id); }) layerLegend.layerId = "layer1"; layerLegend.subLayerIds = layerIds; legendLayers: [layerLegend], */ const template = new PrintTemplate({ format: 'pdf', layout: 'a4-landscape', layoutOptions: { authorText: 'Blah', titleText }, }); const params = new PrintParameters({ view: this._view, template, }); // // NOTE: Start the print progress spinner // this.printProgress = true; const printURL = 'https://utility.arcgisonline.com/arcgis/rest/services/Utilities/PrintingTools/GPServer/Export%20Web%20Map%20Task'; PrintTask.execute(printURL, params).then((result) => { // // NOTE: Stop the spinner and open the print output // into a new tab. // this.printProgress = false; this.forceChange(); window.open(result.url); }, () => { this.alert.errorDialog('Print Error', 'Please try again or contact support!'); this.printProgress = false; this.forceChange(); }); }   Is there any reason for this behaviour? I'm I missing something in the PrintTemplate or PrintParameters?  On a strange note, I don't use a valueExpression, I always get a legend on the print output: I suspect the problem has to do with the use of the valueExpression, so is there a way to pass my legend / layer information directly to the print task? Thanks ... View more