'Unexpected Null' error in Attribute Rule Validation

GregoryWhitaker — Tue, 13 Jun 2023 20:44:14 GMT

Hello,

I'm currently building an immediate calculation (update) attribute rule in ArcGIS Pro (2.9x) that basically copies the updated row to a different feature class and adds a few attributes to the copied row from various other tables in the $datastore. I'm still somewhat new to arcade.

One of the table values that I need to grab and insert is not guaranteed to be populated, so I have accounted for this by using an IsEmpty condition before setting the field values to a variable.

The issue I'm having is that, the arcade editor box will not allow me to save and apply the code because the random(?) row that it's pulling to do the syntax validation had a null value before I added the null check. I added a conditional null check afterwards realizing that I had forgotten to do so, but it still does the same. As a last resort, just to get the rule saved, I calculated out any null values in the field of concern, also to no avail. It almost seems like pro is caching values somewhere or the validation is stuck, but I've cleared the project cache, created a new project, and re-added all the layers, so I don't think that is it.

Code is below. The offender is ggsFilter.GGS . I have also tried == null as well as the DefaultValue() commented out below it. Also probably worth noting that all the field values are coming in with the ggsFilter, so it's not that there's an empty object.

Any pointers or ideas would be greatly appreciated! Thanks in advance!

Re: 'Unexpected Null' error in Attribute Rule Validation

JohannesLindner — Wed, 14 Jun 2023 07:23:33 GMT

When you call First() on an empty Featureset, it will return null. You're trying to call an attribute of null, which raises the error.

if (IsEmpty(ggsFilter) || IsEmpty(ggsFilter.GGS)) { //... }

You're missing null checks in your return dictionaries, too. These might pass evaluation, but they will raise errors on execution if you encounter empty filtered Featuresets. An easy way to handle these would be IIf():

if ($feature.EDIT_RESPONSE == 'Abandon') { var fieldMap = [ { "attributes": { //from StructureBoundary // bla //from COMPANY "COMPANY_NAME": IIf(companyFilter == null, "Default Value", .COMPANY_NAME), "OPERATOR": IIf(companyFilter == null, "Default Value", companyFilter.IS_OPERATOR),

Re: 'Unexpected Null' error in Attribute Rule Validation

GregoryWhitaker — Wed, 14 Jun 2023 14:09:29 GMT

Hey, that worked. Thank you @JohannesLindner for the help!!

I now see how that error was happening--I had forgotten to account for the sample validation record not having a match and therefore returning an empty filter. I didn't think to check the filter itself as well as the field value.

Best,

-Greg

topic Re: 'Unexpected Null' error in Attribute Rule Validation in ArcGIS Pro Questions

'Unexpected Null' error in Attribute Rule Validation

Re: 'Unexpected Null' error in Attribute Rule Validation

Re: 'Unexpected Null' error in Attribute Rule Validation