topic Re: Problems trying to implement attribute rule example in Pro documentation in ArcGIS Pro Questions

Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Fri, 24 Jan 2020 14:24:10 GMT

Hello everyone,

I'm trying to implement essentially the same functionality as in one of the examples in the Pro documentation at Attribute rule script expression examples—Geodatabases | ArcGIS Desktop, specifically:

var fsStructureBoundary = FeatureSetByName($datastore, "Substation", ["name"], true)

var fsSubstation = Intersects(fsStructureBoundary, Geometry($feature))

var substation = First (fsSubstation)

var subname = ""

if (substation == null)

return {"errorMessage": "Transformers must be created in a substation."}

else subname = substation.name

return subname + " - " + $feature.assetid;

Of course my feature class names are different, but when I validate the expression I get:

Invalid expression

Error on line 1

Table not found {FC}

I've tried the FC name as it appears in the TOC, the name of the source FC in the geodatabase, and the full Database.DBO.FC source all with the same result.

What am I missing?

Re: Problems trying to implement attribute rule example in Pro documentation

HusseinNasser2 — Fri, 24 Jan 2020 15:19:30 GMT

Hey Andrew,

That error means that FeatureSetByName could not find the table name {FC} Means the table {FC} could not be found. Can you paste your script and a picture of your geodatabase schema?

The `$datastore` global in FeatureSetByName must be your geodatabase workspace, so make sure that the table Name you specify is the physical table name in your geodatabase not the layer name.

Hope that helps

Here is a video of the talk I gave back in Dev Summit 2019 in Attribute rules with demos from scratch

Attribute Rules in Arcade Video | Esri

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Fri, 24 Jan 2020 17:35:07 GMT

Thank you Hussein! It looks like I had to get the FC name in there without the gdb.DBO. prefix AND get the field name containing the attribute in there to get it to recognize the table.

The expression now checks as valid. HOWEVER, when I go to save the "Applying changes" progress bar just rolls and rolls.

Do these attribute rules have to be applied before services are published from these feature classes? Does versioning/archiving have to be off? Any details like that I should be aware of?

Re: Problems trying to implement attribute rule example in Pro documentation

HusseinNasser2 — Fri, 24 Jan 2020 18:05:13 GMT

Hey Andrew,

Yes you only add the "gdb.DBO." prefix if you are not the owner of the dataset. if you owner the dataset you can just use the name of the class.

Attribute rules are considered schema change so all connections should be closed before a change can be done.. this includes stopping services. (Exclusive lock required)

You can add them to any dataset with any registration type versioned or unversioned.

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Fri, 24 Jan 2020 18:33:42 GMT

Thanks again Hussein!

Quick clarification on the gdb.DBO thing - this rule is designed to take effect when other users add points to the FC thru Collector. Since they aren't owners, do I need to explicitly put in the gdb.DBO, or is it only when authoring the rule where that applies? In other words, once the rule is "in there" since I put it in and don't need the gdb.DBO, will it evaluate correctly when others insert points?

Re: Problems trying to implement attribute rule example in Pro documentation

HusseinNasser2 — Fri, 24 Jan 2020 18:55:24 GMT

Assume you have a user called "gdb" and you connected to the workspace with "gdb" user , you can create the attribute rule using FeatureSetbyName ( "gdb.dbo.TreeTable" ). You can also just say FeatureSetbyName ( "TreeTable") (you can do that because gdb owns the table). Regardless what you write we will ALWAYS persist it internally fully qualified "gdb.dbo.TreeTable" If a user "test" try to connect to the workspace and tried to execute the attribute rule (made an edit) then it will query the table "gdb.dbo.TreeTable" which means test must have access to the table "gdb.dbo.TreeTable"

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Fri, 24 Jan 2020 19:58:18 GMT

Perfect. Thank you for all your help. One more for the road: How could I turn this script inside out and say "If a polygon contains a point from a specific fc, calculate a field attribute in the polygon fc to 'yes'"?

Re: Problems trying to implement attribute rule example in Pro documentation

HusseinNasser2 — Sat, 11 Dec 2021 15:23:10 GMT

The correct way of implementing this is little bit more complicated. The easier way can be by having one rule on the polygon class that activates on insert/update and does the query and populate the field. but the problem with this approach is if you move the points then the polygon fields are no longer consistent, you will have to go and make a bogus edit to the polygon to activate the attribute rule.

assume you have the following schema

polygonClass (fields: hasPoint)

pointClass1

//rough script on the polygon class to the hasPoint field

var fsPointClass1 = FeatureSetByName($datastore, "PointClass1", ["objectid"], false);

if (Count(Intersects(fsPointClass1, $feature)) > 0)
    return "yes"
else
   return "no"‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Mon, 27 Jan 2020 12:22:02 GMT

This is perfect Hussein. Thank you!

I do sheepishly have to say I did think of another attribute rule application question over the weekend. I'll post that in a separate thread as it's slightly different in scope (I think).

Your assistance has been extremely helpful. Thank you again!

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Mon, 27 Jan 2020 12:34:18 GMT

BTW Hussein, this is probably a big enough and useful enough topic that you could write a very successful book on the subject. These tools may finally give us the ability to build out Collector apps from the desktop that are on par with ArcPad wrt data validation and conditional attribution.

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Mon, 27 Jan 2020 14:51:44 GMT

I may have spoken too soon. For the polygon-attribute-flipping when it contains a point from another fc, it is the *point* that is being created/updated, not the polygon. So we have sample areas polygons that are existing, and when a sample point is taken it get's the ID from the polygon. We then need to simultaneously trigger the polygon to update its hasPoint field to "Yes" since it now contains a sample point. I hope that makes sense.

Re: Problems trying to implement attribute rule example in Pro documentation

HusseinNasser2 — Sat, 11 Dec 2021 15:23:13 GMT

Aha this is a little bit tricky. I will attempt to write the basic version of this but there are so many edge cases that this script doesn't solve. (Moving feature, deleting a bunch of features at once) .. But this is just a start..

Two classes

polygonClass

pointClass

On the pointClass add an attribute rule on insert

//on insert 
//check if we are intersecting a polygon. If yes, set the hasPoint field on the polygon to Yes
var fsPolygon = FeatureSetByName($datastore, "polygonClass", ["globalId"], false);
var intersectedPolygons = Intersects (fsPolygon, $feature);
var polygonFeature = null;
for (polygonFeature in intersectedPolygons) break;
if (polygonFeature == null) return $feature.field; // no polygon intersected found , quit..

//we found a polygon feature set its HasPoint to Yes
return {
          "result": $feature.field, 
          "edit": [
                   {
                        "className" : "polygonClass",
                        "updates": [
                                          {
                                                 "globalId": polygonFeature.globalId,
                                                 "attributes": {"hasPoint": "yes" }
                                      }
                            ]
                   }
                ]

}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

On the pointClass add another attribute rule on Delete

//on delete
//check if we are intersecting a polygon. If yes, make sure we are the last point, if yes set hasPoint to No!

var fsPolygon = FeatureSetByName($datastore, "polygonClass", ["globalId"], true);
var intersectedPolygons = Intersects (fsPolygon, $feature);
var polygonFeature = null;
for (polygonFeature in intersectedPolygons) break;
if (polygonFeature == null) return $feature.field; // no polygon intersected found , quit..

//query the pointClass
var pointGlobalId = $feature.globalid;
var fsPoint = FeatureSetByName($datastore, "pointClass", ["globalId"], false);
var intersectedPoints = Filter(Intersects (fsPoint, Geometry(polygonFeature)), "globalId <> @pointGlobalId"); // find all points that are not me in the polygon

//there are still few points, quit!
if (Count(intersectedPoints) > 0) return $feature.field

//$feature was the last point, .. set hasPoint to No

//we found a polygon feature set its HasPoint to Yes
return {
          "result": $feature.field, 
          "edit": [
                   {
                        "className" : "polygonClass",
                        "updates": [
                                          {
                                                 "globalId": polygonFeature.globalId,
                                                 "attributes": {"hasPoint": "no" }
                                      }
                            ]
                   }
                ]

}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Mon, 27 Jan 2020 15:53:59 GMT

This is very helpful indeed Hussein! Thank you so much. I'm attempting to implement now.

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Mon, 27 Jan 2020 17:08:52 GMT

Close, but running into a problem here.

This is my implementation.

var fsBuffer = FeatureSetByName($datastore, "Section3.DBO.PlannedSoilsSamplngLocationBuffers", ["GlobalID"], false);
var intersectPolys = Intersects(fsBuffer, $feature);
var fsBufferFeature = null;
for (fsBufferFeature in intersectPolys) break;
if (fsBufferFeature == null) return $feature.GlobalID;

//we found a polygon feature set its HasPoint to Yes
return {
"result": $feature.GlobalID,
"edit": [
{
"className" : "Section3.DBO.PlannedSoilsSamplingLocationsBuffers",
"updates": [
{
"GlobalID": fsBufferFeature.GlobalID,
"attributes": {"SampleComplete": "Yes"}
}
]
}
]
}

and this is the error I get:

I think I am mis-interpreting your $feature.field syntax. What field in the point feature class should this rule be attached to? It looks like the only field available is SampleID (the one that is auto-calculated from the previous rule).

BTW, how do you insert that nice code block into the posts?

Re: Problems trying to implement attribute rule example in Pro documentation

HusseinNasser2 — Mon, 27 Jan 2020 17:38:39 GMT

The attribute rules above Are added to a field on the pointClass called "Field" it is just returning the same value indicating a no-op operation (don't do anything)

In your case you can just return the sample Id ($feature.sampleid) and assign the attribute rule..

Your rule is complaining about the table that doesn't exist.. make sure that table Section3.DBO.PlannedSoilsSamplngLocationBuffers exists

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Mon, 27 Jan 2020 17:45:42 GMT

Hmm. yes, it definitely exists. It's the same polygon field that is contributing the SampleID from the previous rule (which works great, BTW. TY!!). I'm very confused as to why it's not finding it. I would think if it didn't exist it would throw an error on line 1 and not validate.

Re: Problems trying to implement attribute rule example in Pro documentation

AndrewZimba1 — Tue, 28 Jan 2020 13:21:49 GMT

Got it now... human error (of course). Thank you for all your help. This has been extremely instructive. Are there any resources that could help expose more of the capabilities of attribute rules? For example, the update of attributes with the edit.[] block is not something I would have even known was possible from the examples shown in the Pro documentation.

Re: Problems trying to implement attribute rule example in Pro documentation

RossFindlay — Fri, 29 Jan 2021 16:23:24 GMT

Hi, I am having a similair issue with an attribute rule I am trying to implement. Took Hussein's "Buffer a Point Feature Rule" and changed the polygon classname to my layer on slqserver.

"className" : "[Sandbox1].[coc\rfindlay].[INFRASTRUCTUREPROJECTS]".

it couldn't find the table. I figured the square braces was the right syntax, Catalog refers to the layer as Sandbox1."coc\rfindlay".INFRASTRUCTUREPROJECTS, and the quotes and slashes i think are making trouble for me.

Any help welcome. Cheers

Re: Problems trying to implement attribute rule example in Pro documentation

RossFindlay — Fri, 29 Jan 2021 19:18:48 GMT

Just a follow up that I did solve my issue.

I created a variable fsBuffer = "InfrastructureProjects" that I then referenced in the "className" line. This passed the value and the buffer was created.