Provide tool to easily remove the field GLOBALID from feature class.

11-07-2012 12:23 PM
Status: Open
Labels (1)
New Contributor III
There are various approaches to remove the field GLOBALID from a feature class, but this should be something out of the box that takes care of this need.  For those that are quite familiar of the hassle of the lack of current functionality for removal of this field please help by voting to promote this enhancement request.

The below snapshot depicts current esri context menu interface functionality to add Global IDs to a feature dataset's feature classes via a right mouse click on a feature dataset.


The below snapshot portrays what esri could do as one option to help ease the problem to remove the field GLOBALID.


Also request esri enhance their ArcToolbox --> Data Management Tools --> Fields --> Delete Field tool to allow deletion of the field/column of GLOBALID.  In turn this would make the software more robust in model builder and python.

If there is an issue that esri doesn't allow the field to be dropped once created thinking it is still part of versioning, replication or related then esri should likewise enhance their product to unregister as versioned as a preliminary step.

We don't want workaround solutions anymore of VB code, ArcObjects when we don't have an ArcObjects specialist on staff, don't want users have to delete from inside MS Access let alone run a script from within MS Access to remove fields nor do we want to use the Feature Class to Feature Class Tool when we just want to work with the source data.  We just want that straight forward solution that is already nearly at our fingertips per above request.

Thanks for your read and consideration.


Agree with the author we do not want to create or find work-arounds for VBA work-a-arounds that are no longer supported.

We experienced this issue for over 40 datasets and it was rather frustrating referencing the Technical Article.
Who wants to deal with 1 feature class at a time?  
Had to create SQL procedures to automate this as it should be out of the box using the ArcGIS tools. For those that need to automate here was our procedure:
Backup GDB
Drop all Indexes on all owned schema tables for Global ID
Drop all constraints on all owned schema tables for Global ID
Drop Global ID on all owned schema tables
Remove Global ID from SDE column registry
Test your versioned environment
obviously this is a hack but the primary reason a tool is needed that is not 1 feature class at a time. 

We need geoprocessing tool to delete GlobalIds from feature class. We use arcpy and geoprocessing tools to create database migration scripts. Without a proper way to delete GlobalIds we cannot rollback our database changes after GlobalIds are added.


Hi all.

KISS. Keep It Simple Stupid: it's very easy to enable Global ID and Editor Tracking through Arcpy, as well as to disable Editor Tracking thanks to Arcpy. But NOTHING for Disable Global ID...!

The only way to get rid of it: transfer from a GDB with GID to the same without GID (yes I know, quick to be done thanks to Load Dta and a good XCross, but that means "Production Mapping" extension (which we fortunately have) for something basic...

Hard for me to tell all my French and international partners to use Data Reviewer if it is so hard just to get rid of Global ID to go back to their original GDB structure (meaning without GID and Editor Tracking fields that are compulsory for most Data Reviewer attribute rules...)

Best regards, keep on getting the best!



So I was doing some work with an end-user and after troubleshooting something to deal with GlobalIDs, I said, no worries just use the search bar and type in: Remove GlobalIDs


Surprise. Surprise. This ArcGIS Idea from 2012 still valid and relevant 11 years later.


There needs to be an easier way to remove a GlobalID that does not require recreating a feature class.


Great tip, @RonnieRichards. It would be great if you could share the SQL that you used to delete the Global ID column in your RDBMS.

11 years and still no fix for this? I'm quite weary of the way ESRI treats us.