Renumber auto generated identifier property

Renumber auto generated identifier property

toolbox2
Advocate Advocate
700 Views
5 Replies
Message 1 of 6

Renumber auto generated identifier property

toolbox2
Advocate
Advocate

Novice here.

 

I've created an SDF file; defined my schema; and have defined a property to be an identifier and its value auto-generated by AutoCAD Map.

 

All working so far but after adding and deleting a few features etc I'd quite like to renumber the identifier property.

 

Can this be done?

0 Likes
Accepted solutions (1)
701 Views
5 Replies
Replies (5)
Message 2 of 6

ChicagoLooper
Mentor
Mentor

Is it possible to provide a little more info about your sdf and your goal?

  1. Can you upload a screen shot of the sdf's Table View?
  2. What attribute (or column) in the table are you trying to edit?
  3. What edit (or end result) are you trying to achieve? 

 

 

Chicagolooper

EESignature

0 Likes
Message 3 of 6

parkr4st
Advisor
Advisor
Accepted solution

Copy and save the original data just in case of .....        after the edits, check in.  mapimport the data with all FDO data except FeatId.  Mapexport the objects to a new FDO file with the object data selected for attributes.  The FeatId should be sequential in the new file.

 

dave

0 Likes
Message 4 of 6

toolbox2
Advocate
Advocate

Ahh, looks like I have more learning to do. The FeatID property does indeed get recreated and renumbered but I've now lost my data. The schema is still defined, kind of, just the data I manually entered prior to the mapimport/export has gone. For example, I had property that I defined as Boolean but now is an integer.

 

I'll keep trying but what steps could I have missed during MapImport/Export?

0 Likes
Message 5 of 6

ChicagoLooper
Mentor
Mentor

My 2 cents....

 

An sdf's Feature ID (FID) is a unique identifier used by M3D to identify each and every record. Unlike other attributes, for example zip code, which can be shared among the records, no two items in your data can have the same FID. This is not only good but necessary because without a fool-proof way to differentiate one record from another, M3D would get confused.

 

From what I see, you are trying to use the sdf's FID for your own personal purpose, whatever that may be. Making the FID do double duty might, by coincidence be possible, but doing so, as you already know, is not without consequences. What started off as an unique identifier used by your data, it is now an edited number arbitrarily determined by you for you.

 

Since you are the sdf's author you can append your data to include another attribute, for example 'DemoNo' where you use integers such as 101, 102, 103, 201, 202, 203, 301, etc. With proper planning, the DemoNo attribute can be established by you during sdf creation. Unlike the FID, it can not only be edited, you can also use it to sort while you are in Table View.

Chicagolooper

EESignature

0 Likes
Message 6 of 6

toolbox2
Advocate
Advocate

Thanks for the pointers. Turns out that a Bulk Copy also renumbers the FeatID.

 

I now realise I'm going about this the wrong way.

 

Just as you suggested, I need to create my own editable, but unique, ID property.

 

The only reason I asked about renumbering was because I though that once I've made edits and deletions etc I could renumber the reference number, just once, before I make the information live.

 

0 Likes