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 calculations failing in Web Editor and Web Map forms, but not Field Maps

DBurek

I've been running into a handful of issues with calculated expressions in forms on the web. These calculations seem to work fine in Field Maps, but not in the Web Editor or Map Viewer. In the Web Editor, I'm getting failed to calculate errors when adding new features. In the Map Viewer, it just spins forever, and the form never loads, whether adding or trying to edit existing features. I've been trying to troubleshoot by logging info to the console, but those messages don't show up in the console in my browser (Chrome) if the field fails to calculate, so that isn't very helpful. I have found that if I remove parts of my code that look at certain fields, I can get it to succeed. I need to check those fields for the calculation to do what it's supposed to do, though. I've tried structuring the code to check if the problem fields are empty before checking their values, or checking if it's an insert operation vs an update. It seems that just having any of the problem fields anywhere in the code, even if it's in a line that shouldn't be executed in a particular situation, causes the failure.

Here is an example of a calculation that fails:

Console('*LOG*STATUS* Edit Type: ' + $editcontext.editType)
Console('*LOG*STATUS* Origin: ' + $feature.origin)
Console('*LOG*STATUS* Deprecation Date: ' + $feature.date_deprecation)
//Console('*LOG*STATUS* Complete Date: ' + $feature.date_complete)
Console('*LOG*STATUS* Invoice Receivable: ' + $feature.invoice_receivable)
Console('*LOG*STATUS* Type A: ' + $feature.type_a)
if ($editcontext.editType == 'INSERT') {
  return 'Planned'
} else {
  if (Includes(['Reference', 'Existing'], $feature.origin)) {
    return $feature.origin
  } else if (!IsEmpty($feature.date_deprecation)) {
    return 'Deprecated'
  //} else if (!IsEmpty($feature.date_complete)) {
  //  if (IsEmpty($feature.invoice_receivable)) {
  //    return 'Complete'
  //  } else {
  //    return 'Closed'
  //  }
  //} else if (!IsEmpty($feature.type_a) || (!IsEmpty($feature.photo_count) && $feature.photo_count != 0)) {
  //  return 'Partial'
  } else {
    return 'Planned'
  }
}

If I uncomment the parts that check date_complete or photo_count, it will fail when inserting, even though the first part of the if would be true.

Is this a bug, or am I missing something in my code?

Find more posts tagged with

Arcade

Accepted answers

DBurek

Thanks, @MErikReedAugusta, for your help with this. I managed to get to the bottom of at least part of the issue. Turns out it was the calculation that I was doing to set the value for photo_count that was causing the issue. I was just doing Count(Attachments($feature)) originally. I updated that to IIf($editcontext.editType == 'INSERT', 0, Count(Attachments($feature))) and it started working in the Web Editor. It still spins forever in the Map Viewer, so that is likely a different issue. I don't necessarily need things to work there, so it may not be worth figuring that part out.

Now I'm on to another problem with calculations not saving into the feature attributes. I will create a separate post about that if I can't get it working after spending some more time on it.

Thanks!

All comments

MErikReedAugusta

Some exploratory thoughts/notes:

Line 15 seems to be the only place you use a positive IsEmpty, rather than a negated IsEmpty. If I'm following your logic correctly, I think that's fine, but you might want consider flipping the logic here someone looking behind you doesn't miss the difference and get confused.

Line 14–19, does it work if you uncomment the outer part, but not the inner part? Try the following:

else if (!IsEmpty($feature.date_complete))
{
  return 'TEST_STATE'
}

Line 20, you check if photo_count is not equal to 0, instead of whether or not it's greater than zero. What happens if someone puts a negative there somehow? Should it fail? Does it fail?

Also on Line 20, you have nested boolean logic AND you're checking a NULL state and a value at the same time. I can't remember if the latter breaks in Arcade or not, but it often breaks in other languages I'm used to like Python.

First, I'd consider splitting this to two else-if statements: One to check $feature.type_a, and one to check $feature.photo_count
Second, for $feature.photo_count, I'd consider nesting the logic. This is the part that routinely breaks on me in Python, for example. NULL cannot be compared to an integer, so it crashes out. Off the top of my head, I can't remember how Arcade handles these.
Those two together are going to make for some slightly redundant code, but if it works exploded like this, then you know you're dealing with unexpected boolean shenanigans. I find "simple and parseable" beats "non-repetitive" almost every day.

<...>
else if (!IsEmpty($feature.type_a))
{
  return 'Partial'
}
else if (!IsEmpty($feature.photo_count))
{
  if ($feature.photo_count != 0)
  {
    return 'Partial'
  }
  else
  {
    return 'Planned'
  }
}
<...>
else
{
  return 'Planned'
}

Also, since this appears to be a text field, you could always try dummying up something as a Console in the text field, rather than writing your intended value. "return `Photo_Count:${$feature.photo_count}`", for example.

DBurek

Hi Erik,

Thanks for your reply.

Line 15: Good thought. I will make that change to make it clearer.

Line 14-19: If I uncomment the outer part, it fails to calculate. In fact, if I uncomment the Console call to log the value of date_complete (or even just to log if it's empty or not), it will fail.

Line 20: That attribute is calculated in another expression. It's null until it gets calculated, then it will be 0 or more. It's just getting a count on the number of attachments the feature has.

Also on 20: I originally did not have the !IsEmpty in there, but I thought maybe that was the reason for the error. I thought that Python evaluates the parts of the if in order and only if needed, so it wouldn't check the value of photo_count if it's null, since the comparison in the parentheses is already false. I assumed Arcade would be the same. I tried expanding it just now as you suggested, but unfortunately, it still fails.

MErikReedAugusta

The Console bit is especially odd. That almost makes me think there's some corrupted/invalid data in the table, somehow.

If you have the time to sink into it, I would try one or both of the following two things:

New Feature Class

Create a new feature class with a date field called "date_complete" and give it whatever domain constraints are on your current field.
Now create "date_test1" and "date_test2" fields. Test1 should be DATE, where you're just trying to forward the value, and Test2 should be TEXT, where you can try to output test strings like this script.
Write an Arcade script to copy over the date value to Test1 (when one exists), and see if works. Now write an Arcade script to write a test string based on whether you have a date. Both tests should succeed. That will confirm we're not dealing with some sort of weird bug or logic error. If they fail, that's your issue.

Truncate & Test

Make a copy of your existing data, and delete all records from the copy.
Create a few fake records by hand in the copy and run the script in your original post, to see if it fails.
1. If it fails here, you might have a corrupted table somehow.
If all goes well, delete all the fake records, and start appending data from your source a little bit at a time, and running the script.
1. If it fails somewhere along the line here, then you know you have a corrupted value somehow.

DBurek

To be clear, this code is not a script that is running on the entire feature class. It's a calculated expression that is run in the form when adding new or editing existing features. The issue isn't isolated to a particular feature or handful of features. It happens every time. So I don't think a corrupt value could be the issue. I tried creating a new layer based on this one and created a few test features in it. The same issue is occurring there.

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.