Latest Contributions by JoelBennett

Setting resultGraphicEnabled in the sample with 4.31 works as well... ... View more

My bad, just saw you were using 4.31.  I'll check the samples with that version. ... View more

It does sound like a bug, but since it works in the samples, I'm not sure what to say about it.  Are you also using 4.32? The code I gave is the "autocast" syntax, so should work without the constructor: const invisible = { type: "simple-marker", style: "square", color: [0, 0, 0, 0], size: "8px", outline: { color: [0, 0, 0, 0], width: 1 } }; sources.forEach(searchSource => { searchSource.resultSymbol = invisible; });   I'm not certain it'll make a difference, but may be worth a try.  Other things would be to delete your temporary internet files (i.e. clear your cache), and user your browser's developer tools to ensure you see the latest code, and it's actually being executed by placing breakpoints, etc. ... View more

It seems to me that setting resultGraphicEnabled to false should have done it, but since it didn't, there are alternatives.  For example, sources is a collection of SearchSource objects.  Each of those has its own resultGraphicEnabled property, so you might try setting those to false. If that doesn't work, SearchSource objects also have a resultSymbol property that allows you to define the appearance of the selection symbol.  You might try setting that property with a completely transparent symbol.  For example: //SimpleMarkerSymbol for points { type: "simple-marker", style: "square", color: [0,0,0,0], size: "8px", outline: { color: [0,0,0,0], width: 1 } }   or //SimpleFillSymbol for polygons { type: "simple-fill", color: [0,0,0,0], style: "solid", outline: { color: [0,0,0,0], width: 1 } } ... View more

After testing, I've concluded this was fixed in 4.32 since the situation described above now works without having to apply any fixes. ... View more

The object referred to as "esriId" is the esri/identity/IdentityManager module.  A shortcut to the documentation of the registerToken method is here. ... View more

Did this end up working out, or did you find something else more suitable? ... View more

As far as I can tell, your code looks fine.  Here's something to look into though: Your query's where clause "1=1" will return every record in the layer (this is and of itself is fine). Your console window only shows one record, which itself appears to be fine. However, it's possible that one record somewhere in the midst of all the records returned by the query has a null geometry.  Such a case could cause the problem you're seeing.  In that case, you might want to add a check to see if a record has a geometry before processing it. ... View more

Aloha Noah, thanks for following up.  Your example uses the Shape_Length field, so doesn't exhibit the problem, since that's a numerical attribute.  The problem I'm running into appears to happen when using the Geometry function.  In your example, I changed the expression to: expression: "Round(Length(Geometry($feature),\"feet\"),2)"   In doing so, I was surprised to find it working.  I then changed line 22 to use version 4.31, and the labels stopped appearing, although there weren't any errors in the console.  It appears that perhaps this may have been fixed in 4.32.  I haven't started testing with 4.32 yet, but plan to later this week or next.  When I do, I'll try this issue out and see what happens. ... View more