Latest Contributions by JoelBennett

This is practically identical to this post.  Have you tried the solution proposed there? ... View more

After looking into this a little further, I've found the Search widget calls the locator.suggestLocations method, which returns an array of SuggestionResult objects that differ slightly than the SuggestResult objects you mentioned above.  These SuggestionResult objects do contain the isCollection property, but that information gets lost in esri/widgets/Search/support/locatorUtils when they get transformed into SuggestResult objects. @Noah-Sager any chance that isCollection values can get carried over into SuggestResult? ... View more

I think you can fix this by not setting the FeatureLayer's outFields to ["*"].  Instead, I believe you should limit the outFields to just the ones you want to search, .e.g ["name","alternate"]. ... View more

Without seeing your code, it's impossible to tell what's causing the problem.  However, to accomplish what you're trying to do, I would recommend something like the following: var mapCenter = map.extent.getCenter(); var screenCenter = map.toScreen(mapCenter); console.info(screenCenter.x.toString() + ", " + screenCenter.y.toString());   ... View more

I think this may be what you're looking for (may need to double-check my typing for that URL though): const popupStreets = { "title": "Click to report an issue:", "content": [{ type: "text", text: "<b>Street:</b> {SITE_NAME}<br><b>Town:</b> {TOWN_NAME}<br>" + "<a href=\"https://east-riding-self.test.achieveservice.com/service/Map__ArcGIS_Online_Trees" + "?street={SITE_NAME}&town={TOWN_NAME}&USRN={SITE_CODE}&assetID={CENTRAL_ASSET_ID}" + "&Easting={FEAT_CENT_EAST}&Northing={FEAT_CENT_NORTH}\" rel=\"nofollow ugc\">" + "<font size=\"6\">Click Here</font></a>" }, { type: "custom", creator: (graphic) => { const location = view.popup.location; return `X: ${location.x.toFixed (0) }<br>Y: ${location.y.toFixed (0)}`; //gets x/y coordinates } }] };   The most likely issue you were having is needing to escape the quotation marks surrounding the html element attributes, since this text is already inside of a JavaScript literal.  When inside a JavaScript string, if you want a quotation mark in the string, you have to add a backslash before it, like: \" ... View more

It seems to me that if you broke the territories out into individual layers (like you already mentioned), but used a SimpleRenderer instead, you would get much better performance, since that would result in 15 symbols rather than 27,000. ... View more

My apologies...didn't realize this was in the ideas section.  Hope my reply helps though... ... View more

As already pointed out in another thread, the layer order in the Legend is going to match the layer order of the map.  Therefore, if you're going to accomplish what you've described, you're going to have to use more than one Legend control.  In our framework, we create a Legend for each individual layer, and are then free to display those individual Legends in whatever order we see fit. ... View more

The main problem with this is that in 4.x FeatureLayers, you don't have direct access to the Graphic (i.e. feature) objects that are displayed on the map.  The features returned by queryFeatures are a copy of the actual features, and so modifying them won't make any difference to the layer itself. One of the best ways to accomplish what you're trying to do may be to query the features (as you're doing), but then set their symbol property directly, and then add them to a separate GraphicsLayer. ... View more

Got it...thanks also for decreasing the wait time from 3 weeks down to 2 for this release. ... View more