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; } } }

Arcade referencing original feature broken after update

JamieMaxwell

We are getting errors for fields with Arcade calculated attributes after the Field Maps 2025.2 update. It appears to only affect expressions that use the $originalFeature variable. The error message is vague: "10 attributes failed". Was there anything in the latest update that would cause this? Thanks

Edit: Esri has determined this is a bug. BUG-000179854, Description: The $originalFeature function fails when creating a new feature in ArcGIS Field Maps version 25.2, but editing the existing feature is successful.

Trouver plus de publications taguées avec

Accepted answers

All comments

JoryVerhagenWSRL

Has this new update fixed the issues for anybody here?

For me, the problem persists, even using 25.2.2 (iOS) and 25.2.3 (Android). These are the newest versions of Field Maps that are currently available. The version you referenced (25.2.1) didn't fix the issue for us unfortunately.

(Edit: Typo)

DougMorgenthaler

This has been addressed in a recent update on iOS. Esri Support Info

RPGIS

Seems like an expression issue on the server side. It is probably something that a recent update may have caused a java handeling error.

The purpose of the $originalfeature is coded to look at the original record before any changes. For some of the codes it seems like it might be referencing a record that possibly doesnt exist on the first place. Its common in attribute rules to reference a nonexisting record.

SFM_TravisBott

@IngridHogle Can you elaborate on your first Arcade issue? Maybe provide an example? I am having a similar situation. Post update I had two issues, both exclusive to Field Maps (all worked fine the web maps). The first was with editing the form in the Field Maps designer...I got generic error messages saying it couldn't be saved because there as a problem. I removed all of the fields from a group a and re-added them and that fixed it.

My second issue, which your post might speak to, involves an if/else statement to declare a variable in a pop-up. It uses html and works just fine in the web map as-written, but with certain templates it shows an error for the pop-up in Field Maps. It's generic (ArcGIS.InvalidCallError error 1), but I've narrowed it down to the logic around declaring a variable.

ChristopherCounsell

Feel like I'm going crazy a bit. Had seen this thread so though it might be related

Get loading icon and no form when creating a new feature from template
Arcade has a mix of $originalfeature, edit mode = insert, if statements, GetUser($layer).username, now(). Using variables and accounting for if inserting or updating i.e. no original feature reference on insert
Remove the arcade, form starts working
Add the same arcade calculations back in, form continues to work

Suggests there was some temporary performance hiccup but there's no other indications e.g. everything worked fine on 25.1, ArcGIS Online, and 25.2 when interacting with the layer outside of creating a new feature.

Logs have one line but it's not super helpful

8/10/25, 2:44:07 pm [SNAPPING] NOT activating snapping because not editing any features yet or it's disabled
8/10/25, 2:44:07 pm [LOCATION] Stopping location provider
8/10/25, 2:44:07 pm [LOCATION] Unregistering request MainMapViewModelImpl
8/10/25, 2:44:04 pm [ARCADE] FeatureFormViewModel.evaluateExpressionsAndUpdateUI() - Cancelled, not updating FeatureFormItems
8/10/25, 2:44:04 pm [SNAPPING] NOT activating snapping because not editing any features yet or it's disabled
8/10/25, 2:43:34 pm [REFRESH TASK] Cancelled refresh task request for identifier: com.esri.fieldmaps.task-list
8/10/25, 2:43:31 pm [REFRESH TASK] Successfully scheduled refresh task for identifier: com.esri.fieldmaps.task-list
8/10/25, 2:43:29 pm [SNAPPING] NOT activating snapping because not editing any features yet or it's disabled
8/10/25, 2:43:29 pm [AUTHENTICATION] Removing Handler: Cancel Handler: Load Map Items-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
8/10/25, 2:43:28 pm [TASKS] Notification permission denied: wasPreviouslyDenied - true
8/10/25, 2:43:28 pm [LOCATION] Starting location provider
8/10/25, 2:43:28 pm [LOCATION] Registering request MainMapViewModelImpl
8/10/25, 2:43:28 pm [TASKS] Created tasks capability
8/10/25, 2:43:28 pm [AUTHENTICATION] Removing Handler: Cancel Handler: Load Map-AB3B726C-BB72-442B-AFB4-F3AD60BD19A8
8/10/25, 2:43:28 pm [LOADING] Loaded map xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
8/10/25, 2:43:28 pm [MAP TOOLS] Not creating IPS, no indoor positioning definition
8/10/25, 2:43:28 pm [SPATIAL UNIT] Not creating SpatialUnitCapability
8/10/25, 2:43:28 pm [GEOTRIGGERS] Geotrigger count: 0
8/10/25, 2:43:22 pm [AUTHENTICATION] Adding Handler: Cancel Handler: Load Map Items-1CDA0110-5B15-415D-A944-D4D355EDE675
8/10/25, 2:43:21 pm [AUTHENTICATION] Adding Handler: Cancel Handler: Load Map-AB3B726C-BB72-442B-AFB4-F3AD60BD19A8
8/10/25, 2:43:07 pm [MAP] Failed to provide map: noMaps
8/10/25, 2:43:03 pm [PORTAL] URL: https://www.arcgis.com Mode: AGOL Version: 2025.2.0

alexnJSI

We are also using it in that context, specifically to assess whether or not users have selected a different dropdown menu option. The example was just to simplify it as much as possible.

Regardless of whether or not we are calling $originalFeature.attribute or even just $originalFeature on its own, the error persists. Any calls to $originalFeature in any context are what is causing the bug.

IngridHogle

I've never seen $originalFeature used by itself, so this is out of my league. I always use $originalFeature.something to get some information about the original feature, such as an attribute value, shape area, shape length, or x/y coordinate.

alexnJSI

I did try wrapping any calls to $originalFeature inside of a check for an UPDATE context, but that didn't seem to resolve the error. The code:

if ($editContext.editType == "UPDATE")
{
  var test = $originalFeature;
}
return false;

It does make sense to me that the variable would only be non-null and accessible outside of an INSERT context, but even an explicit wrapper for an UPDATE state produces the same error:

[ARCADE] Expression failed to evaluate:
Name: expr9
Error: invalidArcadeExpression(details: "Arcade evaluation error. Evaluation_error_code::field_not_found Line: 1")

IngridHogle

Can you try putting your expression inside an edit context condition like this (filling in an existing attribute for what I named value)?

var test = ""

//if this is a new feature

if ($editcontext.editType == 'INSERT') {

test = "new feature test";

// if this is NOT a new feature,

} else if ($editcontext.editType == 'UPDATE'){

test = $originalFeature.value;

}

return test

alexnJSI

We are getting this issue in any Arcade calculated expressions within Field Maps Designer that call $originalFeature at any point (which is quite a few of them). The issue can be completely isolated from any other intrinsic functions/variables.

Arcade exceptions are thrown whenever $originalFeature is referenced, including something as simple as

var test = $originalFeature;

and nothing else in the expression.

IngridHogle

I was able to identify that for us, anyways, it is sloppy Arcade expressions I wrote in forms that are causing errors in Field Maps 25.2.0. These are of two varieties:

1. In one Arcade expression, I declared a variable twice (var BlahBlah = "this", then later var BlahBlah = "that"). This worked without errors in Field Maps 25.1.0, but failed in 25.2.0. Removing the second "var" statement, so it reads var BlahBlah = "this, then later BlahBlah = "that", fixes the issue.

2. In multiple Arcade expressions, I invoked $originalFeature without first using an If statement to make sure I was within $editcontext.editType =='UPDATE'. This worked without errors in Field Maps 25.1.0, but fails in 25.2.0. It makes logical sense to me that it would fail, since $originalFeature does not exist (there is no original feature) in the context of $editcontext.editType == 'INSERT'.

RPGIS

My recommendation is to test whether the feature geometry has changed in comparison to the field values.

var fx = $feature.UTM_X
var fy = $feature.UTM_Y
var G = Geometry($feature)
if( G.x != fx && G.y != fy ){
    return { result: { attributes: Dictionary('UTM_X',G.x,'UTM_Y',G.y) } }
    }
/*
Note: the code above will update both fields with the changed values if
there are values that have been updated in the field.
*/

That way it will only need to compare the latest changes to the geometry change. If there is a change it will update accordingly.

JamieMaxwell

@DougMorgenthaler , it's happening on iOS with Field Maps logged into ArcGIS Online. Online only, have I have not tried offline. Seems to only happen when creating new features.

DougMorgenthaler

@IngridHogle can you please provide some additional details.

What platform(s) are you seeing this error?
Occurring while using connected map, offline, or both?
Are the expressions being used in a pop-up, form, or elsewhere?
Can you share examples of expressions that are failing?

DougMorgenthaler

@jmaxwell_braun can provide some additional information to help us understand the issue a bit more.

What platform(s) are you seeing this error?
Occurring while using connected map, offline, or both?
Is the expression failing only when updating an existing feature?

JamieMaxwell

I opened Esri case number 04012489. For me it only affects certain expressions. For now I'm just disabling them so our field staff are able to work.

IngridHogle

The calls just started coming in from staff that multiple Arcade expressions are failing for us after last night's update, and they cannot work as a result. 😞 I'm not sure what to do so I'm posting here in hopes of adding some urgency to this situation.

JamieMaxwell

Hi Cody, here's an example.

//sets value of calculated coordinate field to null only if the location of the point is edited
//if only attributes are edited, the coordinates remain the same
if(!IsEmpty($originalFeature))
  if(Geometry($originalFeature).x != Geometry($feature).x)
    return null
  else
    return $feature.UTM_X
else
  return $feature.UTM_X

CodyPatterson

Hey @jmaxwell_braun

Would it be possible to show a bit of the code? There may have been a depreciation that is causing this.

Cody

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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