nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding field to Versioned Enterprise Geodatabase

Lebowski

I have run into some problems in the past and I just want to verify the steps to properly 'unversion' my Enterprise Geodatabase in order to add a new field in multiple feature classes:

1. Reconcile all versions

2. Delete versions except for the default

3. Unversion database

Could someone please verify these are the necessary steps so I can avoid any complications?

Thanks,

Chad

Find more posts tagged with

Accepted answers

Robert LeClair

Chad - the data owner of a versioned feature class can add a new field without going through the whole process of unregistering and re-registering. Once the data owner creates the new field, it is seen in all versions.

Regards,

Robert LeClair

Esri-Denver

All comments

Robert LeClair

By "ruins" the whole database, what do you mean? Since there's only 1 feature class (that is versioned), adding an attribute field would be seen across all versions.

chadh

I have found that not to be true. I have done that before and it "ruins" the whole database

Robert LeClair

Regards,

Robert LeClair

Esri-Denver

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.