topic Re: Arcade - Parse Error: feasuresetbyname is not available in ArcGIS Online Questions

Arcade - Parse Error: feasuresetbyname is not available

LiqiongSong1 — Thu, 17 Jan 2019 00:10:33 GMT

Hi I tried to use the new function FeatureSetByName in a Demo ArcGIS Online Map, and got below the errors, featuresetbyname is not available.

Then I tried it in Portal for ArcGIS and got below the error: Execution Error.

Does anybody have the same problem? any suggestions?

Thanks all

Re: Arcade - Parse Error: feasuresetbyname is not available

XanderBakker — Thu, 17 Jan 2019 12:49:35 GMT

Where are you trying to apply this expression? Is it in symbology or in the label expression? If so the FeatureSetBy* functions are not available there. Another aspect to validate is the type of layer you want to do this on.

Re: Arcade - Parse Error: feasuresetbyname is not available

LiqiongSong1 — Thu, 17 Jan 2019 23:17:46 GMT

The layers are polygon and point feature class.

And I tired to use the function on 'Change Style' -- 'New Expression' and 'Create Labels' - 'New Expression'.

Could you please tell me where can I use the function in Web Map?

Thanks.

Re: Arcade - Parse Error: feasuresetbyname is not available

LiqiongSong1 — Fri, 18 Jan 2019 00:26:36 GMT

Thanks for the reply, and I tried it in Pop up, it works fine, so it's just not available in symbol or label...

Re: Arcade - Parse Error: feasuresetbyname is not available

XanderBakker — Fri, 18 Jan 2019 11:54:09 GMT

That is correct. You can however symbolize a layer on a field created using FeatureSetBy* functions. To achieve this you should add the field and do a field claculation. The downside is that it will not be dynamic.

Re: Arcade - Parse Error: feasuresetbyname is not available

LiqiongSong1 — Mon, 21 Jan 2019 03:59:55 GMT

Oh, thanks, will try it on!

Re: Arcade - Parse Error: feasuresetbyname is not available

Scott_Sambell — Tue, 18 May 2021 22:28:23 GMT

Hi Xander. When will we have access to FeatureSetBy* in labels and symbology? Symbolising related records is the single biggest issue we have had with FieldMaps/Collector for the past 5 years and we have created some epic workarounds but none are ideal. (Before you ask, we cannot use the Join Features (View) function as all our work is offline enabled and Views created this way cannot be taken offline.)

Is there a feature request i can +1 and add my workflow examples to?

Thanks.

Re: Arcade - Parse Error: feasuresetbyname is not available

JLBlair — Fri, 21 May 2021 18:15:44 GMT

Hi Xander, can you point me to an example where you "symbolize a layer on a field created using FeatureSetBy* functions" as mentioned above? I'd like to show only those points (stations) that are in wildfire polygons.

Re: Arcade - Parse Error: feasuresetbyname is not available

AarjenPeeters — Thu, 07 Apr 2022 15:26:25 GMT

Hi @Scott_Sambell
We are having the same problem. We also want to symbolise related records. What are your workarounds for this, as this is still an issue?
Thanks,
Aarjen

Re: Arcade - Parse Error: feasuresetbyname is not available

Scott_Sambell — Sun, 10 Apr 2022 07:49:06 GMT

Hi Aarjen

We have been through a few workarounds. We were using the Join Feature method (which doesn't work offline so we had to create an offline replica of the feature service using a dodgy ArcPro model), then we started using a mix between a scheduled ArcPro model and Geoevent Server to keep a cached feature service updated and we could almost keep everything updated in near real time but Geoevent server is wildly unreliable so we ended up having to reboot it everyday just to keep it going so, now we are finally using FME, running as frequently as the machine can possibly handle with a single engine to update extra fields in the parent that are populated by the most attributes from the most recent record in the child table to symbolise and label the parent features.

Its insane but this issue has taken up a good proportion of my adult life and i still can't understand why this isn't Esri's highest priority to provide a solution for out-of-the-box.

Re: Arcade - Parse Error: feasuresetbyname is not available

DanieldaSilva — Wed, 14 Dec 2022 13:02:55 GMT

Hi Xander,

When using field calculation, are the calculations a once off or the data in the calculated field is constantly updated as the data changes?

Re: Arcade - Parse Error: feasuresetbyname is not available

LindsaySpencer — Mon, 30 Jan 2023 21:41:00 GMT

@Scott_Sambell and anyone else interested, please kudos if you are still needing this functionality here!

https://community.esri.com/t5/arcgis-online-ideas/update-arcade-profiles-to-include-visualization/idc-p/1244445#M9640