Bug
The ArcGIS Pro Arcade expression builder fails to detect if the item returned from a First function may be null when the input array is from a filter function that filters data based on numeric attribute fields.
| Bug ID Number | BUG-000167914 |
|---|---|
| Submitted | May 30, 2024 |
| Last Modified | August 2, 2024 |
| Applies to | ArcGIS Pro |
| Version found | 3.3 |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | As Designed |
Additional Information
When using the First function always add a null check, at runtime if the passed featureset to the First function has no rows, the First function returns null. The validations done both by the expression builder and the at save attribute rules are very basic and do not catch all runtime errors, just like any other programming language. The expression builder uses the first row in the table if no rows are available in the table, an ephemeral in-memory row is created with default values to be used for validation, and the in-memory row is also used during save time. The expression builder may or may not catch the null error, the same thing with at save. So it is always recommended to handle null checks in the script.Workaround
When using the First function always add a null check if the returned row is null. That is because the featureset might be empty.
Steps to Reproduce
Bug ID: BUG-000167914
Software:
- ArcGIS Pro
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App