nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

scope of variables

TracyLove · 2025-07-13T18:57:00+00:00

* Is there any possible way to store a variable such that it can be used during the creation of successive features? For example a survey team ID or a reservoir level for bathymetric temperature readings. So the scope of operation is really the field map when it is opened. * Is there any way to store a variable that can be…

TracyLove

Is there any possible way to store a variable such that it can be used during the creation of successive features? For example a survey team ID or a reservoir level for bathymetric temperature readings. So the scope of operation is really the field map when it is opened.
Is there any way to store a variable that can be accessed by any of the arcade expressions associated with a form? So the scope is just within each new features data entry form. For example in my case, multiple fields need to access attributes in the previous record..

var lastRecord = FIRST(ORDERBY($layer,'created_time DESC'));
seems like my field map would run a lot faster if i was not running that query for each field.

Find more posts tagged with

Accepted answers

All comments

There are no accepted answers yet

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.