Latest Contributions by calebmelies1

I was able to resolve this but I still think it should have worked with the first code I posted.  By checking the database after every entry, I figured out that any fields not being edited were getting the wrong value. By switching from $feature.attribute to $originalFeature.attribute I was able to get the desired results. if ($originalFeature.JobStatus == $feature.JobStatus){     return $originalFeature.JobStatusLastEdit } else {     return Now() } ... View more

I added zipCodes to the FS and no dice. All other attribute rules run as expected with the expected outcomes. The only rule not working over REST is the rule updating Shape. I went ahead and wrote a database trigger straight to SQL Server as a work around. ... View more

One more note... This does work when adding a feature on a map connected directly to the DB but not when adding a feature on a map connected to the Feature Service.  And Config Popups on the Feature Service map can't find the zipCode layer via $datastore?  This works in the map connected to the database. ... View more

Michael Miller Config Pop-ups with scripts is great advice for saving time (I encourage my team to do this when possible)!  For this application, we are storing zip code center points.  I have tested the script in the pop-up and it works as expected.   ... View more

I just noticed I am in fact getting the error when editing the feature service in Pro. Here is a screenshot of the script (also in text below). I tried to keep it as close to the ESRI example I referenced: //This calculation attribute rule is added to the shape field of a point feature class called pointClass2 var centerFeature = First(FeatureSetByName($datastore, "density.DBO.zipCodes")) //Get the x and y values of the feature in the pointClass1 var x0 = Geometry(centerFeature).x var y0 = Geometry(centerFeature).y //Get the x and y values of the current feature in the pointClass2 var x1 = Geometry($feature).x; var y1 = Geometry($feature).y; var x2 = 0; var y2 = 0; var d = 5 //Calculate the euclidean distance from feature in pointClass1 and current feature in pointClass2 var d1 = sqrt((x1 - x0) * (x1 - x0) + (y1 - y0) * (y1 - y0)) //Calculate the new x and y to be within 5 metric units while maintaining slope x2 = (x1 - x0) * d / d1 + x0; y2 = (y1 - y0) * d / d1 + y0; //Create a point geometry from the new x and y values var pointA = Point({ "x": x2, "y": y2, "z": 0, "spatialReference": Geometry(centerFeature).spatialReference }); return pointA ... View more

Hi Xander Bakker‌, I thought the same thing about Pro/Portal/API all using REST to make edits. I've included a screenshot from Postman below. I've also tested other attribute rules on non-geometry fields and those update as expected using this method. ... View more