Generating Unique IDs with Attribute Rules

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.
---------------------------------------------------------------------------------------------------
Follow us on Social Media!
Twitter: / esri
Facebook: / esrigis
LinkedIn: / esri
Instagram: / esrigram
The Science of Where: www.esri.com

[@bnmoody05]

This wasn't working on my Enterprise GDB (MS SQL server) data. So I modified it to "return NextSequenceValue('Sequence_Name')" and it works like a charm

[@adityarajchavada3364]

Thanks for sharing the video. Can this be used on any existing attribute field with versioning workflow?

[@armgeo6246]

is this also work with arcgis desktop 32bit? thanks

[@Nivlaek5thAge]

All features are created within an ArcGIS Pro file geodatabase and then are loaded into an Enterprise SDE which has more fields that apply to the dataset. I need to be sure that every time I load new data I don't duplicate uniqueIDs. The SDE database would be the official version of the data for the public to see. Certain customers want to link their data to our data and need to be sure they can rely on a uniqueID. Is this the best route to do that? I just make sure the uniqueID field within the ArcGIS Pro feature class exists on the SDE side of things when I LOAD the data into SDE?

[@rachelbu1881]

Thanks for sharing the video. If I use attribute rules in a feature class, does it create an object in my geodatabase? Does it work on both ArcMap and ArcGIS Pro?

[@faisalalinn9423]

Thanks. Will this work with the VERSIONING scenario?

[@geez8699]

How can apply this to a feature class that already have 2000 points created? To apply the IDs to already created features?

[@ivanparaordnance]

Thanks for sharing this video, we plan to use immediate attribute rule and NextSequence function to automatically set the bylaw enforcement Case # field to auto-populate with the next Case #. Example, 21-00001 would be the first record in year 2021, 21-00002 will be second and so on until the year changes to the next on December 31 then we need to re-set the counter to zero and update the year. Example 22-00001 for first record in 2022. Do you have any suggestions how to implement that? Thanks