I want to be able to save Arcade Expressions in AGO. Business case: I wrote an arcade expression to style a layer. I then clicked the "reset to default style" button and saved. And to my chagrin, it blew away my recently written arcade expression ... requiring me to rewrite the expression so that I could use it instead of the default style, after I changed my mind.
Yes -- this is still an issue. I've used Arcade in Dashboards and have had to create a separate text document to save my script when (not if!) it gets wiped out from some other change. It's very frustrating.
And I just experienced this in a StoryMap when using a Field Calculator to concatenate fields and incorporate HTML for formatting. When I go back into the FC, I can't see what was used -- it would be really nice if the script saved.
An Arcade Library that can be used in multiple layers, in multiple web mapping applications would be great! It would be like creating a global parameter at the organization level. They could even be shared to groups and outside orgs if needed.
I see this a lot when creating some arcade expressions that are referencing feature layers based on the feature location. Being able to include this in the popup for all of the layers in a web map would be huge.
I agree wholeheartedly. And on a related note, please don't wipe out the existing symbology every time we edit the expression!
I'm not very optimistic that ESRI will end up implementing this, but an Arcade Library of some kind would be such a big help. I've configured a number of expressions for pop-ups and labels for one of our feature layers across a variety of maps. We recently experienced a bug from the June 2025 update, and the 'fix' for that is going to wipe every single one of those expressions out. I now have to go through every web map to save those pop-up configurations in GitHub or a separate repository manually, which is going to take a very long time and put a lot of other projects on pause.
It would be very nice if I could just store those expressions in a repository within AGOL so that I don't have to do all of this manual work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.