topic Re: Attribute Assistant Autonumber Method in State & Local Government Questions

Attribute Assistant Autonumber Method

JoeBorgione — Thu, 25 Aug 2016 14:47:07 GMT

In this discussion https://community.esri.com/thread/181774-how-is-auto-increment-supposed-to-work a couple of ideas were tossed around, and Jake Skinner‌ suggested using the AUTONUMBER method to sequentially increase a unique ID.

I just gave this method a try for the first time and it does not seem to work for me. I would like to deploy this method on the MASTER STREET NAME table within the LGIM and right now I'm working with a small test set of records. Prior to adding this method to the DyanmicValue table , I added a new field of long int type, calling it MASTERSTREETS_ID and calculating all the existing records to equal the OID, just to establish the numbering sequence. I then added a new record to the DynamicValue using the AUTONUMBER value method, setting the On Create field to TRUE and the On Change to false. According to http://solutions.arcgis.com/shared/help/attribute-assistant/tools/attribute-assistant-methods/#autonumber

there is no Value Info needed, so I left it <NULL>.

However, when I add a new record, I get a value of 1 in the MASTERSTREETS_ID field. Not what I was hoping to get. I must be missing something but not sure what....

jskinner-esristaff‌

mlhotz‌

mmiller-esristaff‌

Re: Attribute Assistant Autonumber Method

JoeBorgione — Thu, 25 Aug 2016 18:10:44 GMT

The answer was right in front of me the whole time... In the other thread I reference, Mark Hotz provides a screen shot of his DynamicValues table. All I had to do is add the words "No Value" to the Value field; I was taking the online help literally....

Re: Attribute Assistant Autonumber Method

MikeMillerGIS — Sat, 27 Aug 2016 00:57:45 GMT

Actually, if should be null. This method is not using the value info. We are using a few methods internally to determine the existing Max number in the field. Was your data a table or a feature class? Also, was it stored in a Enterprise GDB or a file GDB?

Re: Attribute Assistant Autonumber Method

JoeBorgione — Mon, 29 Aug 2016 00:04:25 GMT

mmiller-esristaff‌; It's a table in a 10.3.1 File Geodatabase; it didn'twork for me until I put the words No Value in the Value Field. So it's supposed to work with <null>? I'll be back on site in couple of days and look closer at it then.

Re: Attribute Assistant Autonumber Method

MikeMillerGIS — Mon, 29 Aug 2016 12:35:12 GMT

Joe,

I was able to find a bug with the autonumber and tables. I have made a fix to resolve this and it will be available in the next release.

Re: Attribute Assistant Autonumber Method

JoeBorgione — Mon, 29 Aug 2016 14:16:48 GMT

I wondered about that after my last post.....

Re: Attribute Assistant Autonumber Method

JoeBorgione — Wed, 19 Oct 2016 19:34:33 GMT

AMuise-esristaff‌ Hey Allison- I noticed you marked Michael's answer as correct; any idea when the next release will be?

Re: Attribute Assistant Autonumber Method

AllisonMuise1 — Thu, 20 Oct 2016 20:39:43 GMT

Sorry, I don't have a date for it yet.

Re: Attribute Assistant Autonumber Method

JeffreyWarren — Fri, 21 Oct 2016 11:40:11 GMT

I'm jumping in a bit late here, but couldn't you use the 'Generate_ID' method to get the same results? That is what we use to generate our ID's for all of our features.

If you want to keep your original ID's, just do a sort and find the highest number, then create a record in the GenerateID table called MasterStreetID (or whatever) and put the ID that you found above in the 'SEQCOUNTER' and interval it by 1. Then create a record in the DynamicValue table for your masterstreets_ID and use the generate_ID method. Works well for us. Below is an example from our set up. We have a field that contains our old ID's and I did exactly what I mentioned above. Then I use the generate_ID method to get the next number. We also use our map Grid (not necessarily needed for streets) in our ID so, using an expression I combine the grid w/the oldid column (which is autonumbered now) and we get our unique ID.

Re: Attribute Assistant Autonumber Method

JoeBorgione — Fri, 21 Oct 2016 11:45:45 GMT

Yes, that's exactly what I've done, but the auto number method dosen't require the additional table and associated maintenance.

Re: Attribute Assistant Autonumber Method

JeffreyWarren — Fri, 21 Oct 2016 12:29:02 GMT

I agree. I believe the generateid table is best for when you have multiple feature classes that you want to share an ID sequence. We are in the scenario where we have fittings, manholes, inlets, etc. that our departments want to just call S-*123, because they are all "structures", even though they are each in their own feature class. So, autonumber would not work for us. And granted there really is no maintenance per se, just the time to create the 1 record in the generateid table and add the record in the dynamic value table. Just depends which flavor you prefer. Good luck.

Re: Attribute Assistant Autonumber Method

JoeBorgione — Fri, 21 Oct 2016 13:24:22 GMT

Having a more 'universal' id make does good sense. I'm going to take a closer look at that, as it may prove handy in my application as well. Thanks!

Re: Attribute Assistant Autonumber Method

MikeMillerGIS — Fri, 21 Oct 2016 19:24:32 GMT

We are targeting February for the next release.

Re: Attribute Assistant Autonumber Method

JoeBorgione — Fri, 21 Oct 2016 20:41:26 GMT

Cool.