idea Allow Editing on Fields with Arcade Calculated Expressions in ArcGIS Field Maps Ideas

Allow Editing on Fields with Arcade Calculated Expressions

JoshuaFlickinger — Tue, 22 Aug 2023 23:25:09 GMT

Idea

Allow fields to remain editable when an Arcade Expression is used to calculate them.

Reasoning

Calculated expressions are great at improving efficiency in field operations, but in advanced use cases they don't always work the way I expect them to. Some of it may be user error on my part, but because I can't rely on my expressions, I generally end up not using them. Allowing the field to remain editable would increase usability in the shoulder cases where my expressions fail to return expected results.

Example

I provide GIS support for a forest monitoring crew. The crew maps trees in plots and fills out a bunch of information about each tree. To keep track of trees over time, each tree gets a unique identifier. I wrote an Arcade expression to create the tree ID on the fly whenever a new tree is mapped. The expression uses a geometry intersect to determine which plot the tree is in. Then it counts all the existing trees in that plot and adds 1 to the number of existing trees. Finally it returns the plot and tree number in a nicely configured format.

Works like a charm, when it works. Unfortunately, it doesn't work when the accuracy threshold for data collection hasn't been met. In these cases, no point exists to do the geometry intersect, but arcade still proceeds with the calculation. It looks like it errantly picks the first plot in the list by default and returns me a blatantly wrong ID. Would be great if I could go back in and manually input the ID in these cases.

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Wed, 23 Aug 2023 00:20:43 GMT

I agree that sometimes it would be useful to be able to edit a pre-calculated value. In our use cases it would be that the field returns the users Name or ID, but sometimes they might be filling it out on behalf of someone else and would need to change the name to someone elses.

@JoshuaFlickinger in your current situation where the accuracy isn't good enough to make the intersection - have you considered adding a buffer to the intersection? It would act like adding a search distance. You can also add an IIF statement to return "Unknown" instead of the first random value if it fails to find a search. The buffer would be useful if there's enough space between plots to ensure that you can still find the one you need within a reasonable tolerance. I've listed a code I use below for you to review.

var BufferedFeature = Buffer($feature, 20, 'meters') //Adds 20 metre buffer to the feature geometry before intersecting var intersectLayer1 = Intersects(FeatureSetByName($map, 'FPC Plantations'),BufferedFeature) //Searches this layer 1st. var intersectLayer2 = Intersects(FeatureSetByName($map, 'Planned Establishment Areas'),BufferedFeature) //If no value found above, searches this layer //Search of Layer 1 - returns value in field "Name" - if empty, then runs search on Layer 2 for(var f in intersectLayer1) { if(!IsEmpty(f.Name)) { return f.name } } //Search of Layer 2 - returns value in field "Name" - if empty, then returns "Unknown" for(var f in intersectLayer2) { if(!IsEmpty(f.Name)) { return f.Name } } return "Unknown"

Re: Allow Editing on Fields with Arcade Calculated Expressions

lah — Wed, 23 Aug 2023 13:08:17 GMT

This is absolutely needed. 90% of the time the calculated value may be the correct one, but there is always an exception that we need to account for. My team has been unable to take advantage of this functionality because there is not a single use case where we would want to force a value on someone.

May be a duplicate of this idea: Calculated Default Values

Re: Allow Editing on Fields with Arcade Calculated Expressions

MappyIan — Wed, 13 Sep 2023 15:47:39 GMT

Being able to edit calculated fields is the very first problem we hit when trying to implement Field Maps. As others have said, calculated fields are correct for about 90% of the time, but sometimes you need to be able to edit the calculated value. I really don't see why a field can't be calculated, and then editable if the value is not correct.

It would be awesome if this could be implemented.

Re: Allow Editing on Fields with Arcade Calculated Expressions

cbp-geus — Thu, 25 Jan 2024 08:19:41 GMT

We experienced a similar issue with our field season using a field expression in our ArcGIS Field Maps app. Our geologists wanted the locality number to be filled out in a sequence automatically based on the first locality they make, so they don't have to remember each new locality number. In total they usually collect over 2700 localities in a field season.

We use a simple field expression from two fields to get a sequential locality number and a unique locality name, but we discovered that when our field geologists edit their collected localities, e.g., adds a new photo attachment or update their field notes, the sequence number is also updated in the geodatabase, which is very unfortunate. We are debugging our code now to see how we can prevent that, but our field geologists want to be able to also edit/correct the calculated field value them self if needed.

//Create a sequential locality number var previousRecord = FeatureSetByName($map, "Locality", ['LocalityNo'], false); var lastRecord = First(Orderby(previousRecord,'LocalityNo DESC')) if (Count(previousRecord) == 0) { return "1" } else { return lastRecord.LocalityNo + 1 } //Create a unique concatenate locality name with locality number var createuser = split(GetUser($layer).username,'_') var createyear = Year(Now()) var locid = $feature["LocalityNo"] Concatenate(createyear,createuser[0],locid)

Re: Allow Editing on Fields with Arcade Calculated Expressions

HollyTorpey_LSA — Fri, 12 Jan 2024 00:55:29 GMT

We really need this functionality, too. There have been so many times when I wanted to add field calculations to make data collection fast and easy 95% of the time but can't because of the 5% of cases when field crews would need to edit the value.

Re: Allow Editing on Fields with Arcade Calculated Expressions

gis_user_ca — Fri, 09 Feb 2024 16:07:07 GMT

This would also be helpful for my workflow where we use Arcade to fill in the nearest feature but sometimes it pull the wrong feature value if there are many features close to the collection point. The user would need to be able to correct the parent value. Bonus point if related records from the corrected feature reautopopulated/corrected the related feature values.

Re: Allow Editing on Fields with Arcade Calculated Expressions

GrantDix — Tue, 27 Feb 2024 22:05:46 GMT

This functionality would be very valuable in our workflows. I want to make forms that are easier for users to use: that prepopulate data when appropriate, but also allow the user to change that value manually if they want/need to. A specific example would be with tree inspections. Lets say last year they identified a bug problem. I want to pull the note from last year's inspection about the bugs into the new inspection, this way the user doesn't need to repopulate that. It even then lets them know that bugs were identified previously as a problem. If the bugs are still there, the user can just save the new inspection with the note. If the bugs are gone, they can remove/change the note and then save the record. This level of functionality, being able to edit/override a value from a calculated expression, would be a major benefit to my organization and workflows.

Re: Allow Editing on Fields with Arcade Calculated Expressions

PamelaKing — Wed, 28 Feb 2024 23:01:26 GMT

This capability would be hugely helpful for us too--for another related reason.

This past summer we had a big issue when we used the calculation "GetUser($layer).fullName" not realizing that this calculation doesn't work if the device is offline (a known limitation that we didn't know about). Unfortunately, using a calculation makes the field un-editable and required. So when our users were collecting data and in a completely offline area, they were unable to complete/submit the form/data because the field was required and the calculation didn't work...and since it wasn't editable there was nothing they could do about it to move forward.

It seems like a small thing to have the users name calculated, but it helps with consistency and is convenient. Making the calculated fields editable would fix these grid lock situations when users are offline, while allowing for the convince when they do have service.

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Thu, 29 Feb 2024 00:16:14 GMT

@PamelaKing interesting - we use the exact same expression for the same reason in offline enabled maps and it works fine both online and offline. For us, it would be useful for staff to be able to override it when they are updating a feature that is not their primary responsibility but for which they are temporarily looking after while someone else is on leave.

Re: Allow Editing on Fields with Arcade Calculated Expressions

PamelaKing — Thu, 29 Feb 2024 15:29:42 GMT

@LindsayRaabe_FPCWA that is really interesting. I wonder if you have some different setting on your device or in your form that let it work--that would be awesome. Even with it working for you, thanks for sharing that the editing would be helpful. I agree!

I am so curious...have you all used the your form/calculation in areas with no service at all? That was when we were having issues. For a while we thought it was just working, but we figured out what was happening was that people were in their offline maps but did have some level of service so the device was able to run calculation.

I just tried the calculation in a test map and put my device in airplane mode to simulate being completely offline and it failed. If you know of a setting that can make it work, please share with me.

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Fri, 01 Mar 2024 00:23:57 GMT

Interesting indeed. Maybe @DougMorgenthaler or @JeffShaner might be able to shed some light on this? Could be that you need to submit a support request through MyEsri to get it diagnosed. Could be a bug based on device type, device OS, app versions, etc.

Re: Allow Editing on Fields with Arcade Calculated Expressions

WetherbeeDorshow — Fri, 01 Mar 2024 00:31:22 GMT

The ability to change calculated fields is absolutely critical. For example, many data entry tasks setting the current date and time as the default is helpful. That said, there are cases when the date must be changed to log something that happened at a previous time/date.

For fields calculated via intersection with arcade, when there are overlapping or adjacent polygons in the layer used to push values to an edit layer, often, the wrong feature is used (based on order of overlap, user's map extent when editing, etc.. ). This is why the intersect picker feature in web app builder is so useful.

For many folks, this is one reason why adoption of experience builder is lagging.

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Fri, 01 Mar 2024 08:02:56 GMT

@WetherbeeDorshow I hear you on the override option for intersected features. We have a similar process in place when an intersected feature is incorrect or simply doesn't exist so it would be good to have manual input options. We do reduce the intersection issues by adding a negative feature buffer to our source feature (which cover large areas) so it reduces the chance of intersecting a neighbouring operation. Maybe thats something that could help in your situation. See my code below and discussion here for how we do this: Solved: Help with returning value from 2 Intersecting Laye... - Esri Community

Note - the code below searches different layers based on selections in other fields, and depending on those, will reduce the search area by different amounts. The side effect is, if a feature is too small to start with (less than 500m or 2000m across depending on the reduction) then it fails to return any intersection and results in the "See Comments" value.

var BufferedFeature1 = Buffer($feature, -250, 'meters') //Negative buffer of 250m to focus search on smaller feature types var BufferedFeature2 = Buffer($feature, -1000, 'meters') //Negative buffer of 1000m to focus search on larger feature types var intersectLayer1 = Intersects(FeatureSetByName($map, 'Plantations'),BufferedFeature1) var intersectLayer2 = Intersects(FeatureSetByName($map, 'Concept Areas'),BufferedFeature1) var intersectLayer3 = Intersects(FeatureSetByName($map, 'Harvest Plan'),BufferedFeature1) var intersectLayer4 = Intersects(FeatureSetByName($map, 'Operation Boundaries'),BufferedFeature2) if ($feature.EstateType == "PTN") {for(var f in intersectLayer1) { if(!IsEmpty(f.Plantation)) { return f.Plantation } } for(var f in intersectLayer2) { if(!IsEmpty(f.PlannedName)) { return f.PlannedName } }} if ($feature.EstateType == "NF") {for(var f in intersectLayer3) { if(!IsEmpty(f.Block_Cpt)) { return f.Block_Cpt + " (" + f.LOIS + ")" } }} if ($feature.EstateType == "SW") {for(var f in intersectLayer4) { if(!IsEmpty(f.OperationArea)) { return f.OperationArea } }} //Repeat the first line for all field1 and field2 values else {return "See Comments"}

Re: Allow Editing on Fields with Arcade Calculated Expressions

PamelaKing — Fri, 01 Mar 2024 14:48:06 GMT

@LindsayRaabe_FPCWA we submitted a support request for this back in July 2023 and was told it is a known limitation. We also submitted an enhancement request (ENH-000157471: Allow Field Maps to support the use of the GetUser() arcade function in a fully disconnected offline environment). I am unable to check on its status though. My agency allows a limited number of users to access My Esri and I am not one of them.

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Fri, 01 Mar 2024 22:15:22 GMT

@PamelaKing I'll see if I can follow up on this myself. It won't show in our account but I'll reach out to support. I'd like to restore my confidence in that it is working properly instead of just nobody complaining about it yet and my Admin role making it work instead when I try it (which has happened before).

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Wed, 06 Mar 2024 01:00:14 GMT

@PamelaKing I've had a chat with Esri support. Here's what they said:

In terms of the the enhancement, ENH-000157471: Allow Field Maps to support the use of the GetUser() arcade function in a fully disconnected offline environment. The current status of this is under consideration, meaning that the product team is considering adding this functionality to a future release.

I've tested this on my device, and it will work in an offline map when I am connected to the internet. However, when I turn wifi and mobile data on the device off the getuser() calculation does not work.

Are you able to test using an offline map and disconnecting the device from the internet?

I look forward to hearing from you.

And a followup up response after confirming it is an issue for us too :

It looks like the issue might be related to the full name function, this must be stored in the Portal, however I have tested the arcade for the username which is GetUser($layer).username and this appears to work offline.

Is the workaround sufficient until this functionality is implemented?

I've since used the below logic to extract first and last names and format them correctly from our Usernames. I hope that helps!

//GetUser($layer).fullName //Use the below if usernames are formatted as first.last@abc_def. //Uses Split to remove text "@abc_def" and then splits the remaining text using the "." //Returns the first and last names fortmatted using Proper case. Proper(concatenate([Split(Split(GetUser($layer).username,"@")[0],".")[0],Split(Split(GetUser($layer).username,"@")[0],".")[1]]," "))

Now , to go about updating all my forms with the workaround!

Re: Allow Editing on Fields with Arcade Calculated Expressions

PamelaKing — Wed, 06 Mar 2024 15:06:40 GMT

@LindsayRaabe_FPCWA Thanks for the update! That is great to hear they are considering it.

That is correct. The code does succeed in an offline map, if the device is connected to service or wifi.

It will not work if we are truly offline (meaning out of service with no wifi). Our users discovered it when they were in an area with absolutely no service and we recreated it by turning off wifi and service settings then attempting to collect data in an offline map. Same result...will not work and locks down the form. Your only option is to discard the form and lose all the data you collected for that feature.

Thank you for the suggested work around. Unfortunately, our agency updated all our accounts last year and our usernames are know our PIV card numbers (2899201405120821460####_usfs) which isn't useful.

Our work around for now is that people have to type in their names. But I am very happy to hear they are considering updating this.

Re: Allow Editing on Fields with Arcade Calculated Expressions

LindsayRaabe_FPCWA — Thu, 07 Mar 2024 00:25:51 GMT

@PamelaKing I don't know how often your users change, but maybe you could consider using a table loaded into the map with the list of user ID's and their name in a separate field. The table could be updated from a source of truth (Azure?) nightly or when users are added or removed using some other process (python?) and the Arcade calculation would use getuser($layer).username to perform the lookup and return the name value. Thats all a bit beyond what I've done with python, but with the right know how, I'm sure someone could make it work. Definitely a lot of working around though compared to GetUser($layer).FullName!

Re: Allow Editing on Fields with Arcade Calculated Expressions

Kevin_MacLeod — Wed, 13 Mar 2024 16:59:23 GMT

Just realized I created a duplicate idea, d'oh. One more +1 on this Idea. Here's another example: Let's say we have a Date_Inspected field. We want to save users time and we put the following Calculated Expression on the field:

Now()

Works great, it sets the current time and date.

What if a user's phone battery died and they got back to the office late. So the following day, they want to enter in inspections. Well, it's going to have the wrong date, it will be today, not yesterday.

Solution: allow users to override a Calculated Expression with their own attribute values input.

When I asked Tech Support (initially I thought this was a bug) they pointed out, this may or may not be the desired behavior. Thus, a simple solution. An option checkbox toggle, to allow users to manually override a Calculated Expression or not to allow it, on a per-field basis in the Smart Form Designer / Field Maps Designer.

In general, we love Fields Maps and Field Maps Designer!