Latest Contributions by HusseinNasser2

‎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

‎08-11-2020

Welcome and thanks for joining the Attribute Rules Place on GeoNet – Let's get started! This is a dedicated GeoNet place for attribute rules. As you explore the group, you'll find tools to connect and collaborate. We encourage you to use the community space to ask/answer questions, share and collaborate on attribute rule scripts, and participate in discussions based on your experiences working with attribute rules. The place will be home to general FAQs, Arcade scripts, real world examples and use cases of using attribute rules, blog posts, videos and much more. To get started we invite you to review the group features on the overview page and familiarize yourself with the featured content, resources, related GeoNet places on the right column. Under resources you will find: Pro Help: Attribute Rules - ArcGIS Pro help documentation on attribute rules. Arcade Help - Arcade help documentation. Find references on Arcade profiles, global variables, and functions. ArcGIS Blogs: Attribute Rules - All ArcGIS blogs related to attribute rules. ArcGIS Blogs: Arcade - All ArcGIS blogs related to Arcade. Arcade expressions: Esri github repository - A github repository of ways to use Arcade with specific sections on calculation, constraint and validation rule examples. Arcade Playground - An online console to test Arcade script expressions. We’re excited to connect and collaborate with you and we look forward to seeing your contributions. - The Geodatabase Team

‎07-21-2020

See how network rules, attribute rules, and arcade can be used to maintain data integrity and obtain insight into your network.

‎07-21-2020

This demo theater session will demonstrate the user experience for adding, viewing, and executing calculation, constraint, and validation rules in Arcade. All from scratch.

‎07-21-2020

An introduction to using attribute rules in enterprise geodatabases. We explain what attribute rules are used for, their different types, how they are authored using Arcade, and the execution models on both the client and server. We will also discuss how attribute rules can generate errors that can be inspected and fixed through the ArcGIS Pro user experience.

‎07-21-2020

Learn some tips to optimize slow arcade expressions with the Geodatabase team. For more information about attribute rules, please visit: http://ow.ly/GjNY50ABgFk

‎06-19-2020

Hello! Hope I can help, the reason the value is getting set to 0 is because you haven't provided a result in the return payload. thus the default will be used.. If you want to preserve the field value you input just simply return it back as follows.. var fsTargetTable = First(FeatureSetByName($datastore, "Totals", ["globalid","gloves_xs"], false)); var glovecount = $feature.gloves_xs; var totalglovecount = fsTargetTable.gloves_xs; totalglovecount += glovecount; var AddList = []; AddList[0] = { 'globalid':fsTargetTable.globalid, 'attributes':{ 'gloves_xs':totalglovecount } }; return { 'result': $feature.yoursourcefieldname, 'edit': [{ 'className': 'Totals', 'updates': AddList }] }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

‎01-30-2020

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

‎01-30-2020

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.

‎01-28-2020

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)

‎01-27-2020

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.

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by HusseinNasser2

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

Welcome to the Attribute Rules Community!

Utility Network Rules, Attribute Rules, and Arcade in the ArcGIS Utility Network

Attribute Rules in Arcade (From Scratch) - Demo Theater

Attribute Rules in Arcade

Optimize Arcade Expressions and Attribute Rules

Re: Field value not preserved when Attribute Insert Rule active

Re: Attribute rules for enforcing attachments?

Re: Attribute rules for enforcing attachments?

Re: Attribute rules for enforcing attachments?

Re: Attribute rules for enforcing attachments?

Split with Attribute Rules

Temporarily Disable Attribute Rules

Merge with Attribute Rules

Re: Attribute rule to merge road centerline addres...

Re: Is it possible to pass dataset name from varia...