ArcGIS should allow the ability to permanently reorder fields in a table

60431
209
04-20-2010 01:33 PM
Status: Under Consideration
Labels (1)
NewingtonConnecticut
New Contributor II

After creating a feature class, it would be convenient to go back after data input, and make changes to the field ordering (position).

209 Comments
Lake_Worth_BeachAdmin

yes yes yes yes. yes again. the workaround in arcpy is a pain in the behind. 

Lake_Worth_BeachAdmin

best to copy a table for test purposes so if anything does blow up it wont matter. 

LukeWebb

Make it simples for us ESRI! 

CattyannCampbell

This has been under consideration for 7 years and still nothing. I started using a third party application called Xtools to do this type of work. 

AngelaPollett

Yes I totally agree! My work around is to use ETGeoWizard

CattyannCampbell

Glad I'm not the only one I've used EtGeoWizard has helped me more times than I can count still using it while I'm waiting for funds to get latest version of XTools since the free trial expired.

XTools allow you to do this without having to create another file can't understand why ESRI can't make this happen

after all these years you would think they would add this to ArcGISPro.

Cattyann Campbell

GIS Administrator

Tompkins County ITS: GIS Division

128 E. Buffalo St.

Ithaca, NY 14850-4207

Direct: (607)274-5418 | Main: (607)274-5417

Web: Main Site<http://www.tompkinscountyny.gov/gis><http://www.tompkinscountyny.gov/gis> , Open GIS Portal<http://tcdata-tompkinscounty.opendata.arcgis.com/>

TinaMorgan1

If you are using an enterprise geodatabase you can create a database view.  You use SQL in the definition to define what fields show up in the view and the order can be defined as well.

For example, if my cities feature class has fields:  OBJECTID, NAME, STATE, SHAPE, and all I want to show is STATE then NAME, then I would create a new view with the SQL "select STATE, NAME from cities", and my output view will only have those two fields in that order.  

Unfortunately, this is not an option for .mdb (personal) or .gdb (file) geodatabases.

AngelaPollett

Hi Cattyann

I totally agree. It’s often important, particularly in large datasets, to list fields in a logical order to make reading and interpretation easier.

Not providing such basic tools just forces users to find alternatives & may result in them loosing customers!

Happy mapping,

Cheers, Angela

Angela Pollett

Senior GIS Analyst (Part-time Monday to Thursday)

Spatial Information

Department of Natural Resources & Mines

P: 07 5451 2402 F: 07 5451 2260

E: angela.pollett@dnrm.qld.gov.au<mailto:angela.pollett@dnrm.qld.gov.au>

W: www.dnrm.qld.gov.au<http://www.dnrm.qld.gov.au/>

AngelaPollett

Thanks for the tip Gina. Unfortunately I use file GDB.

Nice to know there are so many helpful people out there though ☺

Cheers, Angela

Angela Pollett

Senior GIS Analyst (Part-time Monday to Thursday)

Spatial Information

Department of Natural Resources & Mines

P: 07 5451 2402 F: 07 5451 2260

E: angela.pollett@dnrm.qld.gov.au<mailto:angela.pollett@dnrm.qld.gov.au>

W: www.dnrm.qld.gov.au<http://www.dnrm.qld.gov.au/>

RichEmerson

I think what most people need is a simple geoprocessing tool that will calculate an "order" field, not necessarily change the underlying RDBMS.