|
POST
|
Yes this error means the globalid you passed to the dictionary to update a feature doesn’t exist. You can avoid this by querying the layer and verify that features exist. Before you return the dictionary, do a console and enable logging on Pro arcgis monitor to see the arcade messages. if this is service enable debug on arcgis server manager. alternatively a trick I like to use is to return error message to force the rule to fail and display the message. return {“errorMessage”: text(thedic) }
... View more
Friday
|
0
|
1
|
44
|
|
POST
|
Thanks Ofir for the feedback. We will update the documentation to include the version= option its a valid request. While you can do all of this today through error inspector, we will work on a better user experience in gp tool to allow users to select the version name and expose version specific properties such as evaluating features modified in version.
... View more
4 weeks ago
|
0
|
0
|
94
|
|
POST
|
I authored an example attribute rule to demonstrate this on merge. When the user selects two line features and wants to merge, the attribute rule will pick the largest line segment and copy the addresstext of that line feature to the new merged feature and then the rule will delete the old two segments. Hope this helps //When merging with the option "new feature" the rule will be executed on insert, if we enabled keep original features we get access to the original rows , this way we can query the merged lines, pick the largest segment , take the address from it and copy it to the new merged line. after merging we issue a delete to delete the two original segements.
var g = $feature.GlobalID
var fs = contains(filter($featureset, "globalid <> @g"), geometry($feature))
var biggerAddress = null;
var biggerLine = null;
var tobeDeleted = []
for (var g in fs)
{
push(tobeDeleted, {"globalId": g.globalid} )
if (biggerLine == null){
biggerLine = g;
biggerAddress = g.addresstext;
}
if (length(g) >= length(biggerLine)){
biggerLine = g;
biggerAddress = g.addresstext;
}
}
if (biggerLine == null) return;
return {
"result": {"attributes": {"addresstext": biggerAddress}},
"edit": [{
"className": "main.theline",
"deletes": tobeDeleted
}]
}
... View more
a month ago
|
1
|
1
|
260
|
|
POST
|
I'm not sure if the user workflow allows it but I would suggest using the option to keep the original features and let the attribute rules do the delete instead of the merge tool. This gives you more control as it turns the operation from a delete , update. To an update only and you will write the rule to trigger on update on geometry (use the triggering fields to set the rule to trigger only on the shape change) on the update you will have the control to query the original features (since they won't be deleted) and copy any attribute you want off of it. And then later you can insert the logic to actually delete the original feature. My guess as to why you are losing your update is as you suspected the order of the operations causes your update to be lost/ not persisted.
... View more
10-30-2025
05:20 PM
|
0
|
3
|
322
|
|
POST
|
Hey Mike, if you use the Evaluate Rule gp tool and select the features you want to evaluate , the tool will only evaluate selected features. This isn't currently available when evaluating through error inspector
... View more
10-23-2025
06:04 AM
|
0
|
0
|
114
|
|
POST
|
Make sure to pass in the correct layerid to queryDataElements that belongs to the Utility network layer, if you don't know it you can pass in empty string and that will pull all definitions of all layers which includes the utility network layer. sourceId should be there, if its not, the UN likely wasn't published. Go to to the feature service root json definition and look for utilityNetworkLayerId to see if its published.
... View more
10-14-2025
06:11 AM
|
0
|
0
|
283
|
|
POST
|
Hey Garry, I'm going to assume you are trying to evaluate attribute rules. So first make sure you have batch calculation or validation rules on the class you want to evaluate. then add that class to a new map, and then right click on the layer on the map, you should see a new context menu AddErrorLayers, if you don't or it is disabled this means you don't have batch rules.
... View more
09-08-2025
11:09 AM
|
0
|
0
|
184
|
|
BLOG
|
My colleague Koya has just published a blog detailing how you can performing snapping with Attribute rules. Wherever you are, web, mobile, Pro, edits you make can be made more accurate, and it is configurable. Amazing the stuff you can do with attribute rules. Give it a read! https://www.esri.com/arcgis-blog/products/utility-network/arcade/snapping-with-attribute-rules
... View more
09-03-2025
12:49 PM
|
4
|
0
|
191
|
|
POST
|
I can't tell what is going on but let us verify few things 1) Change the server logs to debug and see if you have entries for attribute rules being evaluated. 2) Does full extent work? 3) create new features and then evaluate them do they get picked up? if that doesn't work Finally try the following. Delete the validation rules, delete the error tables, then add the validation rule again, this will generate the error tables. Makes sure you are using a branch version workspace when you do that. Then delete the feature service and create new map, add your layer and the error tables and publish with the validation server, create a new feature service and test that new feature service..
... View more
08-27-2025
10:23 AM
|
1
|
0
|
347
|
|
POST
|
I would recommend not writing to the association table directly as it can be error prune. Instead use the provided attribute rules dictionary APIs I authored a blog about it https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/advanced-attribute-rules-creating-utility-network-associations-with-attribute-rules for more advanced cases use this keyword Read more here about "^UN_Association" https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/attribute-rule-dictionary-keywords.htm
... View more
08-12-2025
11:01 AM
|
2
|
1
|
332
|
|
IDEA
|
This is now available in ArcGIS Pro 3.5. The user can use Attribute rules backstage options to change the default settings and it will persist when restarting Pro.
... View more
08-11-2025
11:03 AM
|
0
|
0
|
267
|
|
POST
|
This bug has been addressed under BUG-000154445 in 11.1 , and ported to 10.9.1 patch 5, 11.3 should have this fix. If you have a repro case on 11.3 it could be a different bug, I suggest submitting a case. msg me the case number so I can follow up
... View more
08-08-2025
06:44 PM
|
0
|
0
|
261
|
|
POST
|
If you are looking for junction Edge associations you should use featureSetByAssociation($feature, 'junctionEdge') "Connected" is only for JJ associations
... View more
08-05-2025
09:20 AM
|
2
|
1
|
517
|
|
BLOG
|
Alot of customers came to me after the demo I did on the UC 2025 asking for the recording (Which we don't do), so I promised a blog post with code and data instead. Hereit is https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/batch-work-order-generation-with-attribute-rules-uc-2025-demo
... View more
07-25-2025
10:46 AM
|
6
|
0
|
221
|
|
IDEA
|
Yes it is possible to update the same class with attribute rules and prevent infinite loops, I authored a post detailing this with an example. Prevent Infinite loops in Attribute Rules https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/prevent-infinite-loops-in-attribute-rules
... View more
07-24-2025
02:13 PM
|
0
|
0
|
189
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a month ago | |
| 1 | 01-02-2025 06:31 AM | |
| 4 | 09-03-2025 12:49 PM | |
| 1 | 08-27-2025 10:23 AM | |
| 2 | 08-12-2025 11:01 AM |
| Online Status |
Offline
|
| Date Last Visited |
Friday
|