Latest Contributions by JonathanFarmer_oldaccount

Hi Kelsey, I don't think you are missing anything really.  Your geodatabase maintenance strategy looks good, I see no issues there. The only question I have is, why are you deleting the versions? Are you going for a full compress each time you run this? I ask because it goes into your second question. Having to re-register all of those child version connections with Server is expected. See this note below that we include on our page on the topic: "If the database you register contains a versioned geodatabase, ArcGIS Server accesses the version of that data present in the geodatabase version you set for the connection file. If you want ArcGIS Server to access different versions, you must register separate connection files to connect to these geodatabase versions. For example, you may need to register one connection file that accesses the Default geodatabase version and one that accesses a child version."   About registering your data with ArcGIS Server—Documentation | ArcGIS Enterprise  So given that, it seems like deleting the versions each time may not be the best way to proceed. There is a way to get a full compress done without deleting the versions if that is the goal. But getting a full compress done each time you do this is also not necessary. Reconcile and post all child versions to Default Re-reconcile all child versions to Default (without posting) Save edits Compress Doing the above will also get you a full compress if that is the desire and also not delete those versions which means you won't need to re-register databases with Server. Jonathan ... View more

Hey Tom, This is a known issue. But can you confirm that this is your workflow? Add Hosted Feature Layer to a map in Pro Open the attribute table and sort the table based on a field which has a domain Scroll down through the table with your mouse, you should see the error Here is the bug information: BUG-000106410: Sorting a hosted feature layer on a Domain field and..  If your workflow is different, it would be good to know. We'd want to get a new case created in Support and investigate that. Could be we'd need to update this bug or create a new one. But I think this is the bug you are running into. Jonathan ... View more

Hi Todd, You are correct, the Import Map functionality in ArcGIS Pro does not actually move the data anywhere. So if I have a feature class in an MXD that is coming out of an enterprise geodatabase and I use the Import Map functionality in Pro to import the MXD, my data is still in that same enterprise geodatabase. We aren't creating a new connection in your Pro project to that enterprise geodatabase and sourcing the data from there. Hope that makes sense. Besides the usual ways to re-source data in Pro, have you thought about using Python? If you have legacy MXD's with a lot of layers and symbology setup that you don't want to recreate in Pro, you can use Import Map and then use Python to resource all the data. Updating and fixing data sources—ArcPy | ArcGIS Desktop  Once you wrote one script, it would probably be easy to tweak it a bit for each Pro project. But I am not aware of any tools we have in place to do this at the moment. Jonathan  ... View more