Edit operation failed. Message: Unable to complete operation. Details: Unable to perform applyEdits operation. Error: Invalid column value [SUB_YEAR].

Question

Please see the video attached.

I had this functioning properly last week; however, I am now encountering an error message that I believed we had resolved. Please note that this field is not related to the subyear.

This only occurs if we are outside a record.

-_Ashley-B-Potter_- · Answer

@AmirBar-Maor we had to summit a ticket

-_Ashley-B-Potter_- · Answer

@AmirBar-Maor Thank you. I will give this a shot and update accordingly.

AmirBar-Maor · Answer

I have modified your expression

* Account for the situation in which CreatedByRecord is empty = NULL. For example, if someone forgot to create an active record.
* Use the IsEmpty method instead of checking for 'null'
* Only create a FeatureSet if the CreatedByRecord is not empty
* A bit of cleanup

For better performance, you can use the triggering fields to only trigger the rule when the CreatedByRecord field is changed.

Let us know if this helps

var sourceTable = FeatureSetByName($datastore, "ParcelFabric_Records", ["SubYear"], false)
var createdBy = $feature.CreatedByRecord
If (!IsEmpty(CreatedBy)){      //if the CreatedByRecord is not empty
    var fabricRec = First (Filter (sourceTable, "GlobalID=@createdBy"))
    if (!IsEmpty(fabricRec)){ //If the returned record is not empty = record was found
        return fabricRec.SubYear        
    }
}
return "No Sub Year found"