Getting Unique ID using Attribute Rules

[Anonymous User]

Hello,

I am trying to create a Unique ID using attribute rules.

The basic thing I am trying to figure out is to find the max number for field in the attribute table.

For example, looking at the column in the picture below.

When creating a new feature, I would like to set a attribute rules will automatically create the next number.

Which in this case would be 2704.

Using the "NextSequenceValue" seems like the best way to go about but I am not sure how to use this function.

Does "inputSequenceName" work more like how Attribute Assistant works?

Thank you and let me know if any clarification is needed.

[RobertKrisher · Accepted solution]

I wrote a blog post that walks you through getting a sequence and attribute rule up and running ( Configurable Facility ID Creation Using the Utility Network | POWER Engineers  ).  So in your case you'd create a database sequence call something like "sequence_foo" and set the sequence start id to 2705, then you'd set up an attribute rule on your project table on create so that new features get their project number set using the next value in "sequence_foo".

Let me know if I missed the mark on your question or if you want any more details.  Good luck!

[Anonymous User]

Thank you!

This is exactly what I was trying to do.

[melvilegarias]

wow.. thank you ..

i'm looking for this all night...  very helpful ... great..

[tigerwoulds]

The link no longer works. Is this available anywhere else now? 🙂

[RobertKrisher]

Configurable Facility ID Creation Using the Utility Network | POWER Engineers

[KristalWalsh]

Hi, I read through your article but realize that attribute rules don't seem to work unless there is a global id in the feature class or table which is the target of the auto-sequence event.  Is that correct? I have a database  with many relates and want to create auto-sequencing ids that are triggered by 1) a polygon drawn (a feature geometry) or a cell populated by customer information or property information being entered (related tables).  This is a file geodatabase which will be hosted in AGOL and customized for Field Maps. It is not an enterprise database. I've attached an entity relationship diagram and would appreciate any feedback on this. I'm certainly not opposed to changing data types or relates if I need to. This is a fresh build so now's the time to make it right! Thank you in advance. Kristal