|
POST
|
Hey Anthony This is a known bug, the error layer of validation server should be included and packaged in the project package. They are currently not packaged (you get an error when you try) and you will have to add them manually every time. Edit: Bug number BUG-000151105 -Hussein
... View more
10-04-2021
01:40 PM
|
0
|
6
|
2297
|
|
BLOG
|
AmirBar-Maor from the parcel fabrics team wrote a cool attribute rule that allows you to auto-snap to the feature near by after creating or updating a feature. In 2.7, we added the ability to assign an attribute rule to the shape field, which will allow the Arcade expression to return a geometry to update the $feature geometry. This opens up all sorts of workflows, including the one Amir built, which is the snapping. I thought it the attribute rules community will enjoy this https://community.esri.com/t5/arcgis-parcel-fabric-blog/using-attribute-rules-to-update-the-line-geometry/bc-p/1103951
... View more
10-01-2021
08:04 AM
|
2
|
2
|
2180
|
|
POST
|
The utilitynetwork layer id will be different for each feature service. You can find the utility network layer id dynamically for any feature service (if it exists) by querying the feature service definition.
... View more
09-07-2021
11:03 AM
|
0
|
1
|
4276
|
|
POST
|
You can call `queryDataElement` rest call on the feature service and provide the utility network layer id. https://server.esri.com/server/rest/services/service_name/FeatureServer/queryDataElements [13] is the utility network layer id You can find the utility network layer id querying the feature service definition and looking up utilityNetworkdatasetId "controllerDatasetLayers": { "utilityNetworkLayerId": 13 },
... View more
09-07-2021
09:44 AM
|
1
|
3
|
4298
|
|
POST
|
Hey Billy I suggest reading the blog I authored on this topic. It has basic examples of creating associations of all types using attribute rules. The rule you have is so large to debug without the data. I suggest starting with a simpler rule to narrow down whats wrong. It might help to work with a file geodatabase so altering and testing the rule is easier. Then deploy it to enterprise. https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/advanced-attribute-rules-creating-utility-network-associations-with-attribute-rules/
... View more
09-02-2021
08:04 AM
|
0
|
1
|
2294
|
|
POST
|
Constraint rules are always evaluated after Immediate calculation rules in the execution order. I'd like to request few details to understand the context, Is the SQL Geodatabase client server direct connect Or published through a service? And What is the versioning model and DBMS? Also the Pro used and Enterprise Versions. While you get those try the following, turn off "Exclude from application evaluation" on the constraint rules and calculation rules.
... View more
08-24-2021
12:29 PM
|
0
|
0
|
1623
|
|
POST
|
The constraint rule does the following: Only allow features to be edited/created when their status is 1 and the street_id is null. Any other value, fail the edit which is what you are experiencing. You might want to define your logic more explicitly. I'm assuming you want to ONLY fail when the status is 1 AND the street_Id is not NULL. You can specify your logic this way. if ($feature.street_status==1 && $feature.street_id != null)
return false;
else
return true;
... View more
08-23-2021
04:32 PM
|
1
|
0
|
1644
|
|
POST
|
That statement is correct and should work p.s. it is not Arcade, it is SQL.
... View more
08-20-2021
09:05 AM
|
1
|
0
|
1350
|
|
POST
|
You can continue using first but first (no pun) you have to add an additional filter against the polygon you want. Push the query all the way to the DB. var cabs = FeatureSetByName($datastore, "Proposed_OLT_LCP_Boundaries_copy", ["cab_id"], false)
var filteredCabs = filter(cabs, "cab_id='SDY-HUT'")
var cabsInt = Intersects(filteredCabs , $feature)
var cabSpliceInt = First(cabsInt)
if (cabSpliceInt == null) return {"errorMessage": "Please edit inside a cabinet boundary"}
return true;
... View more
08-20-2021
08:14 AM
|
0
|
2
|
1353
|
|
POST
|
FeatureSetByName does not support dynamic class names. The name of the class has to be available during static analysis of the script so we can build out the relations in the catalog. (E.g. if you copy Class A which has an attribute rule that reads from Class B we also copy Class B too) here is more details explaining why Why FeatureSetByName doesn't work with variables https://community.esri.com/t5/attribute-rules-blog/why-featuresetbyname-doesn-t-work-with-variables/ba-p/1541572
... View more
08-20-2021
08:03 AM
|
1
|
1
|
2094
|
|
POST
|
The if statement is an invalid syntax. You are comparing a feature (first(fsResult)) to a value $originalfeature.cab_id. Plus don't use IN, use == instead and compare the actual values That being said, I'm not sure what the rule is trying to do, maybe provide a brief description of what the rule is suppose to do? Going by your statement if you want to prevent deletion of features it is a matter of simply creating a constraint rule that returns false. return false;
... View more
08-12-2021
08:19 AM
|
1
|
2
|
1911
|
|
POST
|
Yes you will need to use the error inspector to trigger the validation rules. That will create an error feature showing you where the duplicates are watch this youtube video where I show how to create and evaluate. Note that you can run validation rules and batch calculation rules on filegdb.
... View more
08-11-2021
05:38 PM
|
0
|
4
|
4162
|
|
POST
|
//detect duplicate var currentAssetId = $feature.assetId var currentObjectId = $feature.objectid var fsMyClass = FeatureSetByName($datastore, "myclass") var fsResult = filter(fsMyClass, "assetid = @currentAssetId and objectid <> @currentObjectId") // search for the same asset id but don't count the current row if (first(fsResult) == null) return true; //we did not find a duplicate else return false; //we did find a duplicate create an error feature A bit slow but should work. Alternatively you can do a summary statistics on the class and detect where count > 1
... View more
08-11-2021
02:01 PM
|
0
|
6
|
4174
|
|
POST
|
Thanks, this is a known bug the Add Error Layer should always light up if your workspace supports validation capability. Right clicking on Anno or dimension layers doesn't allow you to add the error layers, but you can simply right click on any feature layer and that option should be available for you.
... View more
06-01-2021
04:33 PM
|
0
|
0
|
1615
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | 2 weeks ago | |
| 5 | 3 weeks ago | |
| 1 | 4 weeks ago | |
| 1 | 11-03-2025 12:32 PM | |
| 1 | 01-02-2025 06:31 AM |
| Online Status |
Offline
|
| Date Last Visited |
Tuesday
|