Follow-up: I did have a user report that they did attempt to insert data into a SDE Feature class from a shapefile that did not have a defined projection... and then the extents changed radically. That makes sense... well, the reason the extents changed... not as to why we have people still trying to use shapefiles with no projection definition - oh, the humanity!
Easy enough fix for the feature classes using the Property sheet in ArcCatalog or sdelayer -o alter -E for the topology layers (if affected)... but does anyone with 10.3 know how to fix the topology layers extents without sdelayer?
Data loaded from other sources is typically via the copy/paste tools.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.