Latest Contributions by JohannesLindner

    var seg = $feature.SEG_ID var addr = Filter(FeaturesetByName($datastore, "Address_fc", ["STNO", "SEG_ID", "SIDE_OF_RD"], false), "SEG_ID = @seg") var left_addr = Filter(addr, "SIDE_OF_RD = 'Left'") var right_addr = Filter(addr, "SIDE_OF_RD = 'Right'") return{ result: {attributes: { FROMLEFT: Min(left_addr, "STNO"), TOLEFT: Max(left_addr, "STNO"), FROMRIGHT: Min(right_addr, "STNO"), TORIGHT: Max(right_addr, "STNO"), }} }     ... View more

The behavior you want isn't that simple... Your two rules influence each other. The first rule looks at the field that gets changed by the second rule and vice versa. It might be better to do it in one rule:   // Calculation Attribute RUle // field: empty! // triggers: update var lifecycle = $feature.TextField1 var old_lifecycle = $originalfeature.TextField1 var retire_date = $feature.DateField1 var old_retire_date = $originalfeature.DateField1 // Was the date changed to a non-null value? var abandon_feature = retire_date != null && retire_date != old_retire_date // Was the lifecycle changed to "ABANDONED"? var feature_was_abandoned = lifecycle == "ABANDONED" && lifecycle != old_lifecycle // Calculate the new values var new_retire_date = When( abandon_feature, retire_date, // the date was changed by the user, use that value feature_was_abandoned, Date(), // the lifecycle was changed to "ABANDONED", use current date lifecycle != "ABANDONED", null, // the feature is not abandoned, set the date to null retire_date // the feature is abandoned, some other field was updated, use existing value ) var new_lifecycle = IIf( abandon_feature, "ABANDONED", // the date was changed by the user, abandon the feature lifecycle // some other field was updated, use the existing value ) return { result: {attributes: { DateField1: new_retire_date, TextField1: new_lifecycle }} }   Change the field names in lines 5-8 and 31-32. ... View more