We got the Field Maps 22.2.0 update last night. And this morning we can't edit any of our UN features. We get the attached error, "Arcade expression is invalid." We've been using the previous versions with no problem up until yesterday. And Collector still works also. I believe the error is referencing our Attribute Rules which are built with Arcade. However, the UN has many Attribute Rules and we've added several of our own.
We are using iPads with Enterprise 10.8.1 and UN Version 4.
Just as an FYI, it looks like this may also be an issue in the latest release of Field Maps, 22.3.0. I'm hearing reports from our field crews saying they're experiencing issues submitting edits. Is activating the "Exclude from Application Evaluation" for the attribute rules option going to be standard moving forward?
So, we never had this issue until the last two releases of Field Maps. Previous versions of Field Maps worked fine and so does Collector. I logged the bug and apparently it was "fixed" and yet I was still encountering the same issue.
Through some testing, I realized that we had attribute rules which were being calculated based on their spatial relationship with other features. Here's the kicker, we didn't have those other features published in our services used in Field Maps. I recalled that we had this initial issue with Pro when we first moved to the UN last year. And we fixed that by publishing the UN service with that extra feature. So in the end, the fix was to publish the extra features which are used to calculate the attribute rules all in the same service. Or check the 3rd Party Application option.
I guess we were probably experiencing the issue all along but Collector and earlier versions of Field Maps never picked up on this issue until the last 2 releases.
I am having this same issue. Attribute Rules that once executed now present an error when trying to submit the edit in Field Maps. It still works fine in Collector and editing the feature service in ArcGIS Pro also works. Changing the Attribute Rules to "exclude from application evaluation" fixed the issue in Field Maps though.
I am also still getting the same error as before. This happens when adding new features and editing existing features. Using Field Maps 22.2.1.
Can you please work with support to get a case logged? It's likely something specific with your data.
As mentioned, there is a workaround if you check "Exclude from Application Evaluation" for the attribute rules and re-publish the service it should disable client-side evaluation of attribute rules.
This does not appear to be completely fixed in Field Maps 22.2.1 for iOS (Build 751). Still getting "Error: Arcade expression is invalid." when trying to submit attribute edit. The edited attribute is not subject to an attribute rule, but other attributes are, but are not being changed. Did not have this problem pre-Field Maps 22.2.0.
After quite a bit of investigation, Field Maps 22.2.1 for iOS and Android was released with a fix for this.
As mentioned earlier in the thread, another workaround is to check "Exclude from Application Evaluation" for all the attribute rules in Pro and then re-publish the service.
If you still experience issues with attribute rules in Field Maps, please create a new thread or open a support ticket.
The next planned release is at the end of June. This issue will likely result in a hot-fix well before that - the Field Maps and Runtime dev teams are working on a fix.
A potential workaround is to check "Exclude from Application Evaluation" for the attribute rules in Pro. There's a post with more details about this option.
But could you give us a estimate to come out the next release? It's very important for us to define the next steps.
Support wasn't able to give a timeline. I'm hoping it's fixed in the next release since the current work around is to go back to using the now deprecated Collector app.
Good afternoon,We are in a roll out phase of the project for a client and this bug is having a big impact on the delivery time. Any predictions for a resolution? Can't you make the old (stable) version available in the respective stores until the situation is overcome?
BUG-000149094 in case anyone is interested.
Case Number 03057839.
@Anonymous User We reproduced this issue in-house and are investigating. There's no ETA on a fix at this time. If you do open a support ticket, feel free to reference this thread to help speed up the process of getting an official defect logged.
Unfortunately, I don't believe there is a way to roll back. My only advice is to switch back to Collector.
I will submit a case and get you all the case number.
Definitely seems like a bug. To add to the dialog here, we recently updated to 22.2.0 and use arcade expressions fairly heavily and we're met with the same error when it comes to feature edits / record submission. I found an iPad that is still running version 21.3.1 and the issue is not occurring there. Edits are able to be submitted with no error. We're Apple users and are on Enterprise 10.9.1 if that matters. Please help!
I'm assuming there's no way we can roll back a version on the app?
Following- we are using iPads, iPhones, and also testing with Androids. Enterprise 10.9.1.
When you remove the attribute rule on update it works- however this seems to me like a bug.
Our Organisation is having the same issue- updating all features returns the same error with Field Maps 22.2.0 on both Android and Apple. Users with 22.1.0 are not experiencing this issue. This is for both apple and android devices.
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
