Arcade Symbology Errors when Publishing from Pro
Our office is preparing for a field inspection effort and we've run into some weird behavior involving Arcade and maps created in Pro and published out to AGOL.
The TL;DR
Everything we've found essentially boils down to three differing cases:
Upload Path | Arcade symbology written in... | Feature # Correct in Pro? | Feature # Correct in AGOL? |
1. Share As Web Map from Pro 2.9.4 | Pro | Yes | No |
| 2. Share As Web Map from Pro 2.9.4 | AGOL | N/A | No |
| 3. GDB zipped & uploaded to AGOL -> Feature Layer -> Web Map created | AGOL | N/A | Yes |
The Long Version
We've tried multiple variations on Arcade Expressions, and the above behavior always seems to persist no matter how simple or complicated the expression is.
Our most telling test targeted a single field: "EndsInspected", which contains the values 0, 1, and 2.
If we select that field from the field list in AGOL and symbolize, we get the correct feature counts, regardless of upload method. If we instead symbolize on the Arcade expression
return $feature.EndsInspected
we get incorrect feature counts on any map that was published from within Pro. If the map was produced according to Case 3 above, the feature counts are correct.
Below is an image showing the feature counts for our intended two-field expression. It's checking for non-null values in two different inspector fields. This is from our Case 1 attempt above.
I'm still not sure if the error is just in displayed counts in AGOL for the broken cases or if the error is in the underlying data. I'm also not sure yet if the problem's happening on the Pro side (a "pitching" error) or the AGOL side (a "catching" error).
Has anyone else run into behavior like this?
P.S., As an aside to the board administrators: Why is Arcade not an option for the code snippet functionality? Just an oversight?
