Latest Contributions by HusseinNasser2

No they will not work in Collector in offline mode, that is because when we download the data offline the Attribute Rules are not coming back with the data. They will only work on online mode and will be triggered on the server side. In the future releases we will have the capability for Collector and other ArcGIS Runtime applications to download Attribute Rules and execute them locally offline. It is a big project that is in the works ... View more

Apologies I should have mentioned that and Thanks Xander Bakker‌ for reminding me. Yes Validation and Batch Calculation rule are only supported Enterprise Geodatabase Datasets registered with branched versioned. We are bringing the support of File Geodatabase to these type of rules in the upcoming releases soon. ... View more

Thanks Xander! The Attachments arcade function is actually supported on the Attribute Rules profile, we will just need to update the documentation to reflect that. Good find! So yes one can prevent a feature from being created/updated if no attachments was found. However I see this rule fits more as Validation rule instead of a constraint rule (Generating errors for existing features with no attachments) ... View more

Attribute rule is one way to enforce this. You should be able to add a constraint rule to the attachments table of your class that prevents adding a row to the attachment table if the extension is not jpg. You could then publish the class as a feature service to ArcGIS Enterprise and consume it from collector. (Attribute rules not supported on ArcGIS Online yet) Here is an example Here is an example script //if the extension is jpg allow the edit, else don't allow the edit. if (right($feature.ATT_NAME, 3) == "jpg") return true return false‍‍‍‍ The attachment will only be added if the file has a `jpg` extension. There might be a bug where you won't get a meaningful error message back today. We might be able to get to that in the future where the actual error message comes back. ... View more

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 ... View more

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" } } ] } ] } ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

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"‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

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"  ... View more

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.  ... View more