Latest Contributions by HusseinNasser2

‎09-25-2020

Yup you can do this with a calculation rule easily. constrain prevent edits, calculation changes the state of the row.

‎09-25-2020

Yes it is possible, create a constraint attribute rule on an update trigger and use $feature to query the related table to see if object still exist in the related table and block the edit if the object has been severed from the parent. if you found a row that means the object still related, if you didn't that mean the object has just been recently removed and as a result you can block that by return false.

‎09-21-2020

Yes you can perform that task with Attribute Rules using Arcade as a language to write the script. Attribute Rules are currently not available for offline collector use. This will come in the future. Today you can make edits through collector directing to a feature service that has layers with attribute rules and those rules will get executed. that being said , If you take the map offline make edits and then sync back at the time of sync the attribute rules will be executed.

‎09-18-2020

In this video we will learn how to create and work with Validation Attribute Rules, This video is follow up of this one Video Link : 6806 where we learned how to create and publish and enable the validation capability.

‎09-18-2020

In this video we will learn how to create and work with Batch Calculation and Validation Attribute Rules. We will explore the Validation Capability on ArcGIS Enterprise, Error Inspector and much more! Data can be found here: how_to_batch_rules.zip To learn more about Validation Attribute Rules watch this video Video Link : 6807

‎09-18-2020

Hey Joe You can use FeatureSetByRelationshipName to read related records, and you can use DML to update features from other tables. This blog might help Advanced Attribute Rules – Editing features on another class with attribute rules

‎09-18-2020

Here is some more content (video form) on generating unique id Video Link : 6803

‎09-18-2020

Discover how easy it is to create a database sequence for new features in your database using a calculation attribute rule and the NextSequenceValue Arcade function.

‎09-18-2020

Hey Sam are you still running into this problem? We would like to take a closer look and reproduce in the latest software. Can you send us file gdb of a sample data that repro ? would appreciate it It is ok to use PYTHON to calculate your expressions because that will eventually trigger an update on the row which will execute the attribute rule. Thanks Hussein

‎09-18-2020

Yes this is definitely possible, Assuming two tables T1, T2 , T1 is related to T2 via field KEY you will add an attribute rule on T1 and you can have it trigger on update so that it makes an edit to T2 and update the related feature on T1 (find the parent feature by querying T1.KEY = $feature.KEY .. Here is a blog detailing this Advanced Attribute Rules – Editing features on another class with attribute rules You can restrict the attribute rule to execute only if a certain field has been updated by using $originalFeature

‎09-16-2020

Hi David, Thank you for your comment and yes we have thought about bringing native support for Attribute Rules to AGOL however we still do not have a timeline. We will keep you updated for sure.

‎09-03-2020

Sounds like a bug, on split (assuming update-insert split policy) the original feature geometry is updated and a new feature is inserted with all the original feature attributes. This also respects fields with domain with specific domain policy. The fact that the new feature assetId is empty means that this is not the case. I just tried your repro case on fileGDB and it seems to be working. Which platform is this? Geodatabase/Pro/Server all release version so we can identify and repro Thanks!

‎08-25-2020

Glad it helps Vish! Junctions and Devices with no terminals are identical, The difference between junctions and devices are as follows 1) Junctions cannot have terminals while devices can 2) Junctions cannot participate as subnetwork controllers while Devices can I do see your point though with regards to modeling, if you have don't need terminals should you go with a junction or a device. I personally don't see a difference you can choose any. however if you modeled it as a device, you can add terminals later by changing the definition of the device (AG/AT) and magically all your devices now have terminals. You do however need to do some clean up on the data to assign lines/associations to the correct terminals after doing that. If you model it as a junction and then decided to add terminals later you will have to delete all your junctions and physically insert devices in their place and also do the cleanup part to assign terminals correctly. Hope that helps Hussein

‎08-24-2020

Hey Vish, as Paul clarified, no terminals means a single terminal that means its a single path. To satisfy your use case you need fine-grained control over your devices by introducing multi-terminal devices and use "paths" to enable it.. Here is a picture clarify that The first pair is what you have today, notice that the index space it is a single terminal thus a single path. The second pair is what you need, you need a device with 3 terminals (can work with two as well), connect the lines to the appropriate terminals/ports and then define what "paths" are enabled instead of using the network attribute "open" or a "close" you have finer control where you can say path A-B, B-C, A-C..(ALL). You can disable path B-C but allow A-C and A-B and so on.. read more about this topic here Terminals—ArcGIS Pro | Documentation

‎08-13-2020

Hey Courtney, What problems are you having with NextSequenceValue? that should be the solution to get you to sequence your table. 1) You need to create a database sequence, using the Create Database Sequence. 2) Create an Attribute Rule and use the NextSequenceValue to get a sequence from the DB and store it in the field, make sure its on Insert 3) Finally create few features

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by HusseinNasser2

Re: How to update a parent field when a related child field changes using Arcade?

Re: How to update a parent field when a related child field changes using Arcade?

Re: Welcome to the Attribute Rules Community!

Working with Validation Attribute Rules

Create, Publish and Work With Batch Calculation and Validation Attribute Rules

Re: Attribute Rule to Update Feature Layer with Related Table Value

Re: Autonumber in Pro when feature is created in Arcade

Generating Unique IDs with Attribute Rules (NextSequenceValue)

Re: Attribute rules causing failures in field calculations

Re: How to update a parent field when a related child field changes using Arcade?

Re: Welcome to the Attribute Rules Community!

Re: Line split not retaining field of type GUID

Re: More than two lines at a device without terminals

Re: More than two lines at a device without terminals

Re: Autonumber in Pro when feature is created in Arcade

Re: Edit operation failed. Message: Cannot acquire...

Re: Attribute Rule [Constraint]: Combining GetUser...

Re: Attribute Rule [Constraint]: Combining GetUser...

Re: applyEdits in squence - FeatureService vs. Lay...

Split with Attribute Rules