Need Ability to Replace Data Source for Multiple Layers. We can repair more than one layer in Desktop ArcMap, we need the same capability in Pro.
What version of Pro are you using where you do not see this functionality? I purposely broke 2 layers in an mxd and then imported the mxd into a new Pro 2.1.2 aprx. When I click on the exclamation point and fix the link for 1 of the broken layers, the other broken link was also fixed.
Agree with Michael here. Ted Cronin can you expand on this idea? You mention replacing data source for multiple layers and then talk about repairing.
This method does not work for sde databases.
I have a similar issue. (I only just started using Pro)
What is the ArcGIS Pro equivalent of the Set Data Source(s) function in ArcCatalog? (Batch resourcing)
Example: Let’s say I have a .aprx map that has 30 layers in it. Of those 30 layers, 10 are sourced to one.sde, 10 are sourced to two.sde and 10 are sourced to three.sde. For whatever the reason, now I need to source the 20 layers from one.sde and two.sde to four.sde and the 10 from three.sde to five.sde.
In ArcCatalog I would normally use the Set Data Source(s) function to accomplish this task. I can’t find its equivalent in Pro. For Pro, there is a Python script that can batch resource from .gdb to .gdb, but not .sde to .sde, so that doesn’t work for my situation. I’ve talked with ESRI and they’ve said there is a bug (BUG-000112574) when updating enterprise layers with this Python.
Currently, I don’t think there is a way to batch resource .sde sources in Pro. Am I wrong?
Are the links currently broken in your mxd? Or do the links still work, but you want to just change the data source?
The links still work, I just want to change the data source.
The scenario I first talked about is different from your scenario and I totally agree that the Set Data Source tool in ArcCatalog is an extremely useful tool than needs to be ported over to Pro.
In the below post from a month and a half ago I asked if this functionality was available in Pro.
Set Data Sources Tool in Pro
I myself would use this tool when ESRI adds the ability to publish services from Pro directly to ArcGIS Server without the need for Portal (I would use this tool for many other scenarios but the above scenario is a more common workflow for me). I begin with a development SDE database and then need to modify SDE connections to a test SDE database for the test environment and finally modify the SDE connections to a production SDE database for the production environment.
Looking forward to this critical ArcMap Equivalency issue to make it into Pro. Sitting here getting ready for a big project where I need to operate off the network, and this is a very simple operation in Arc Catalog (Point everything to a new FGDB), but pretty much an impossibility in Pro. No, the python method (which doesn't work anyway) is not a solution or a workaround. https://community.esri.com/thread/160714 https://gis.stackexchange.com/questions/301483/seeking-arcgis-pro-tool-to-batch-change-data-sources
Definitely need a tool like the ArcCatalog right click MXD -> Set Data Source(s), to repoint non-broken layers. Users shouldn't have to use the python method for this. It's not unusual for organisations to clean up network drives (changing folder structures etc.), migrate them to new locations with new DFS\UNC\Mapped Drives or for users to have to move from local sources to network sources or vice versa. Any wholesale changes should be scripted but it's not always possible and there'll still be a need for one off updates to specific layers in Pro documents.
They Tried and Failed on this one, there is a python module to do it but it appears to not write anything back into the project.
The workaround doesn't work either.
Any news on when this product plan might move into a version update?
We really need this functionality!
Yes, like change datasource in xtools (v12 and before), it was easy to change datasource from one source to an other. We have, for the same set of data, many source with the same structure. So for one purpose we can point to 1.gdb and an other time to 2.gdb.
It's not a question of broken link.
So the ability to use the "List by dataview" then select the source database we need to change then point to the new one and automatically all layers inside the group with the same structure should be updated.
Retrieving data ...