Latest Contributions by JohannesLindner

Attribute Rules don't work with layers in maps, they work with featureclasses/tables in the same database. Etages has to be in the same database as the fc where you are implementing the rule If the name is different, change it in the expression If you are working in an Enterprise database (.sde), change the name to the full name: DatabaseName.DataOwner.TableName ... View more

For the IDs, see my answer in this question: https://community.esri.com/t5/arcgis-pro-questions/using-attribute-rules-to-create-sequential-id/m-p/1320130   For returning the nearest feature's attributes, you could do something like this: // Calculation Attribute Rule // field: empty! // triggers: Insert, update var other_fc = FeaturesetByName($datastore, "Etages") var search_dist = 1000 // get all features in other_fc within search distance var other_near = Intersects(other_fc, Buffer($feature, search_dist)) // find the nearest var min_dist = search_distance var other_nearest = null for(var f in other_near) { var dist = Distance($feature, f) if(dist < min_dist) { other_nearest = f min_dist = dist } } // abort if no feature was found in the search distance if(other_nearest == null) { return } // copy the attributes return { attributes: { EtaID: EtaID, EtaCode: EtaCode, NivCode: NivCode, } } ... View more

The Attribute Rule needs to know which features it has to update. That is why you have to supply the GlobalID or OBJECTID of the features in the update array. Take a look at the documentation of the return dictionary. Some other problems: You're using an outdated method of appending elements to an array (counter++). If you're using ArcGIS Pro 2.7+ / Enterprise 10.9+, you can use Push(). When you don't find related features, you return a string, but the rule has no assigned field. I don't actually know if that will give an error, but it's useless at least, nobody will see that message. Instead of using Count() (slower) and the error message, just do the for loop and return the result. If the update array is empty, nothing will happen. You're using the values that are already in the asset info table, so nothing will change. You have to use the attributes of $feature You're using assTabList for updates and adds. This will update the features in tbl_asset_info and add new ones, giving you duplicates. What you want to do is this: If you're inserting a new features, use adds If you're updating a feature, use updates // Rule for asset_july_2023 // triggers: insert, update // field: no select // arrays that store adds and updates to the asset info table var assAdds= [] var assUpdates = [] // attributes of the $feature var featureAttributes = { 'ASSET_ID': $feature.ASSET_ID, 'TYPE': $feature.TYPE, 'VALUE': $feature.VALUE } // if this is an insert, add a new asset info feature if($editcontext.editType == "INSERT") { var newAss = { 'attributes': featureAttributes } Push(assAdds, newAss) } // if this is an update, edit all related asset info features if($editcontext.editType == "INSERT") { // value of shared field var key = $feature["Asset_NAME"] // search for related features in tbl_asset_info feature class var assInfFS = FeatureSetByName($datastore, "tbl_asset_info", ["*"], false) var assInfFilter = Filter(assInfFS, "Asset_NAME = @Key") for(var asst in assInFilter) { var update = { "globalID": asst.GlobalID, 'attributes': featureAttributes } Push(assUpdates, update) } } return { 'edit': [{ 'className': 'asset_july_2023', 'adds': assAdds, 'updates': assUpdates }] }   ... View more

Replace line 25 with this: 'incident_date': Number(f.incident_date),   In previous Arcade versions, Date values had to be submitted as Numbers. This problem is fixed in AGOL and will probably be fixed in Enterprise 11.2   ... View more

I can't reproduce the error, but you might want to try these: // your output field is an integer, try rounding Round(($feature.PassengersOutward + $feature.Passengerslnward) / 2) // try using the Mean() function Mean([$feature.PassengersOutward, $feature.Passengerslnward]) // try both Round(Mean([$feature.PassengersOutward, $feature.Passengerslnward])) ... View more

Sorry, should have made that clearer: You can get both from my original solution, I edited it.   ... View more