topic Some Arcade functions are not available in Developers Questions

Some Arcade functions are not available

LanNguyen1 — Tue, 27 Apr 2021 00:29:27 GMT

Hi All,

I started playing with the AGOL/Dashboard/Advanced Editing/Arcade and found there are some functions not available for me. Could anyone shade some lights why they are not available?

Thanks,

Lan

Re: Some Arcade functions are not available

jcarlson — Tue, 27 Apr 2021 01:54:29 GMT

Check out the Profiles page of the Arcade docs. Certain profiles, like working in Dashboards, don't have access to the same global variables that, say, a popup expression might.

Functions which utilize such global variables will be unavailable in such a case.

With Dashboards in particular, the Arcade is already evaluating against a FeatureSet as defined by the element's selected layer, filter, and sort options. Or if it's a per-feature Indicator, for example, you're actually working with a single Feature object, and not even a FeatureSet. In either case, you won't have access to other layers, or even other attributes within the same layer in some cases.

Re: Some Arcade functions are not available

IhabHassan — Tue, 01 Jun 2021 00:27:51 GMT

Hi,

I have posted something similar yesterday, I cannot use "FeatureSetByRelationshipName" for no apparent reason. The Arcade expression fails while testing popup configuration expression.

https://community.esri.com/t5/developers-questions/featuresetbyrelationshipname-arcade-function/m-p/1063283#M5894

Re: Some Arcade functions are not available

JEngvall — Tue, 25 Oct 2022 07:17:55 GMT

Hi,

Did you find a solution/ answer to this?

Re: Some Arcade functions are not available

Ryan_Gould — Mon, 23 Jan 2023 22:44:45 GMT

I had the same issue. I was trying to use a list element with advanced formatting to calculate some statistics. I got it to work by creating a data expression and adding this as a layer in the element.

Re: Some Arcade functions are not available

DarrylAlbert — Wed, 28 Jun 2023 04:54:18 GMT

I am having this problem on a hosted feature layer. Any idea why that may be?