topic Re: Replacing datasource does not work through arcpy in Python Questions

Replacing datasource does not work through arcpy

JoeHershman — Wed, 01 May 2019 18:50:56 GMT

Writing a script to replace the datasource in a project. I have tried doing this by replacing the .sde file path on the apex object. Tried by replacing at the map level and also at the layer level. none of these methods work. It runs without error but open the project back up and everything still pints to the original source.

Following samples located here:

Updating and fixing data sources—ArcPy | ArcGIS Desktop

Has anyone ever gotten this to actually work?

Re: Replacing datasource does not work through arcpy

JoeHershman — Sun, 12 Dec 2021 03:18:50 GMT

This is the basic code that is being used

import arcpy, os, pprint
import traceback
from os import path

project_folder = r'D:\...'
project_file = r'project.aprx'

project_path = os.path.join(project_folder, project_file)
aprx = arcpy.mp.ArcGISProject(project_path)

db_source = 'source'
db_target = 'target'

for map in aprx.listMaps():
    for layer in map.listLayers():
        if layer.connectionProperties == None: 
            continue

        #replace db name in fully qualified dataset name
        source_dataset = layer.connectionProperties['dataset']
        target_dataset = str(source_dataset).replace(db_source, db_target)

        source_info = layer.connectionProperties['connection_info']
        
        # target_info is connection_info dictionary with new parameters
        target_info = dict(source_info)
        target_info['database'] = db_target
        target_info['user'] = 'gis'
        target_info['password'] = 'gis'

        # setup source and target connection_properties
        source_properties = {'connection_info': source_info, 'dataset': source_dataset}
        target_properties = {'connection_info': target_info, 'dataset': target_dataset}

        layer.updateConnectionProperties(source_properties, target_properties)

aprx.save()
del aprx‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Replacing datasource does not work through arcpy

curtvprice — Thu, 02 May 2019 02:59:55 GMT

Seems to me like the updateConnectionProperties method on ArcGISProject (the "apex object"?) is the one you want, as that would be a lot less work!

I suggest going back to trying the method on the project, and add some debug code to your script to verify the connection properties are getting modified at all before you bother to .save(). Another thing to try is set the validate parameter of updateConnectionProperties to False and see what happens.

If [validate is] set to True, the connection properties will only be updated if the new_connection_info value is a valid connection. If it is not valid, the connection will not be replaced. If set to False, the method will set all connections to match the new_connection_info, regardless of a valid match. In this case, if a match does not exist, then the data sources would be broken.
(The default value is True)

Re: Replacing datasource does not work through arcpy

MatthewDriscoll — Sun, 12 Dec 2021 03:18:53 GMT

This is what I use, first I get the current connection info and then replace it using parameters.

import arcpy


arcpy.SetProgressor("1234", "working on updating sources...")

aprx = arcpy.mp.ArcGISProject("CURRENT")

find_dict = {'connection_info': {'user':'username','password':'userpassword','version':'sde.DEFAULT'},'workspace_factory': 'SDE'}

newuser = arcpy.GetParameterAsText(0)
newpassword = arcpy.GetParameterAsText(1)
version = arcpy.GetParameterAsText(2)


replace_dict = {'connection_info': {'user':newuser,'password':newpassword,'version':version},'workspace_factory': 'SDE'}

aprx.updateConnectionProperties(find_dict, replace_dict,"",False)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Replacing datasource does not work through arcpy

JoeHershman — Sun, 12 Dec 2021 03:18:56 GMT

I tried all methods, I only put the sample code for this approach because it is the most granular so I believe as a last effort would show that this does not work. Also my sample has debug code removed as this is not really relevant to what is being done in the functional code. But in all approaches I did as you suggest and had debug code to check if the layer.connectionProperties was changing prior to saving.

Documentation for the method also states:

When working with enterprise geodatabase layers, a path to a database connection (.SDE) file can only be used for the new_connection_info parameter. The information in the .SDE file can't be used for the current_connection_info parameter because the connection information is coming from the layer in the project, not the file. A more complete discussion and examples of connection property dictionaries are also provided in the connectionProperties section below.

Although there is no mention of what should be used as the current_connection_info in this case:

But this has been tried without success

import arcpy, os, pprint
import traceback
from os import path

project_folder = r'D:\...'
project_file = r'project.aprx'

project_path = os.path.join(project_folder, project_file)
aprx = arcpy.mp.ArcGISProject(project_path)

current = 'full path to currect .sde file'
new = 'full path to new .sde file'

aprx.updateConnectionProperties(current, new, False, True)
aprx.save()
del aprx‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I have run inside of Pro and run from Visual Studio, neither working.

Re: Replacing datasource does not work through arcpy

SrihariDarapaneni — Sun, 12 Dec 2021 03:18:58 GMT

Few observations I found from you code,

target_info['database'] = db_target ----- this is not setting the property instead it is 
adding additional values to target_info; may be you can use replace method; arcpy 
don't have rich JSON functions. 

this is source connection property  
{'dataset': 'FeatureClass Name, 'workspace_factory': 'SDE', 'connection_info': 
{'authentication_mode': 'DBMS', 'database': 'FeatureClassName', 'dbclient': 'oracle', 
'db_connection_properties': 'database/instance', 'password': '<*********>', 
'instance': 'sde:'database/instance', 'server': 'serverName',
 'user': 'user', 'version': 'SDE.DEFAULT'}}

but target_properties is{'dataset': 'FeatureClass Name, 'workspace_factory': 'SDE', 'connection_info': 
{'authentication_mode': 'DBMS', 'database': 'FeatureClassName', 'dbclient': 'oracle', 
'db_connection_properties': 'database/instance', 'password': '<****>', 
'instance': 'sde:'database/instance', 'server': 'serverName',
 'user': 'user', 'version': 'SDE.DEFAULT'},{'dataset': 'FeatureClass Name, 
'workspace_factory': 'SDE', 'connection_info': {'authentication_mode': 'DBMS', 
'database': 'FeatureClassName', 'dbclient': 'oracle', 
'db_connection_properties': 'database/instance', 'password': '<****>', 
'instance': 'sde:'database/instance', 'server': 'serverName',
 'user': 'user', 'version': 'SDE.DEFAULT'}}

Make sure db_connection_properties,'instance' has to be set properly based on 
database changes. 

And Also

db_source = has to be existing feature class name, 
db_target = has to be target feature class name

most of the time both are same when we doing one database connection to 
other connection. 

- Problem occurring only when you replacing source info to target info values

- more over tool is not giving errors, this may be bug. 

I am able run the tools successfully.

Re: Replacing datasource does not work through arcpy

JoeHershman — Thu, 02 May 2019 15:20:55 GMT

Seems that maybe the title needs to be changed to cannot replace the 'database' property. I ran your code switching out the 'user' and 'password' and it works as expected. But it does not work if changing the 'database' property. This was one reason I thought going to the layer level might work better because then I could also change the 'dataset' property to the new fully qualified dataset.

In ArcMap I had a process to script changing the datasource and then to publish the maps, save the copy, and publish feature services to a new server from the new maps. This provided a very streamlined approach to moving from dev to qa to prod. As there are over 20 maps this was a big time saver. At this point we will need to do this manually as it seems one cannot change the database through python

Re: Replacing datasource does not work through arcpy

MatthewDriscoll — Sun, 12 Dec 2021 03:19:01 GMT

I see. I think its more important to change the db_connection_properties. Really you should probably change all the connectionProperties when changing to a different databases, it seems you are only changing some of the properties.

Try to find and replace every single property. See the ESRI sample below which includes every property, without joins or relates, I believe.

{'connection_info': {'authentication_mode': 'OSA',                     
                     'database': 'Uhuru',                     
                     'db_connection_properties': 'Dunbar',                     
                     'dbclient': 'sqlserver',                     
                     'instance': 'sde:sqlserver:Dunbar',                     
                     'password': '*********',                     
                     'server': 'Dunbar',                     
                     'user': 'Sly',                     
                     'version': 'sde.DEFAULT'}, 
'dataset': 'Uhuru.SDE.RangerStations', 
'workspace_factory': 'SDE'}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Replacing datasource does not work through arcpy

JoeHershman — Sun, 12 Dec 2021 03:19:05 GMT

This is the original code with debug output to show exactly what is being used as source and replace. This is what happens running inside Pro. I have moved the print output inline to help, also shown at bottom.

The first print shows the connectionProperties on the layer before running any code.
The next shows the same thing but as variable used in the updateConnectionProperties method
The next shows the replace variable. Unless I am not seeing something this is replacing every parameter just using the new settings.
- The database is replaced with the new database name
- The dataset is replaced with the new fully qualified name of the dataset
The final shows the layer.connectionProperties immediately after the replace operation
I did run with the 'workspace_factory' property but included but accidentally copied this output and too much effort to redo the entire code shot below

After that I break out to simplify and only show the single layer

aprx = arcpy.mp.ArcGISProject("CURRENT")
db_source = 'Staging'
db_target = 'fort_collins'

for map in aprx.listMaps():
    print(map.name)
    for layer in map.listLayers():
        if layer.connectionProperties == None: 
            continue
        print(layer.name)
        pprint.pprint(layer.connectionProperties)
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly',
 'workspace_factory': 'SDE'}

        #replace db name in fully qualified dataset name
        source_dataset = str(layer.connectionProperties['dataset'])
        target_dataset = str(source_dataset).replace(db_source, db_target)

        source_info = layer.connectionProperties['connection_info']
      
        # target_info is connection_info dictionary with new parameters
        target_info = dict(source_info)
        target_info['database'] = db_target
        target_info['user'] = 'gis'
        target_info['password'] = 'gis'

        # setup source and target connection_properties
        source_properties = {'connection_info': source_info, 'dataset': source_dataset}
        target_properties = {'connection_info': target_info, 'dataset': target_dataset}

        pprint.pprint(source_properties)
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly'}
        pprint.pprint(target_properties)
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'fort_collins',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': 'gis',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'fort_collins.GIS.PipelineAssembly'}

        layer.updateConnectionProperties(source_properties, target_properties)

        pprint.pprint(layer.connectionProperties)
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly',
 'workspace_factory': 'SDE'}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍
        break
    break
Map
Pipeline Assembly

# connectionProperties on layer
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly',
 'workspace_factory': 'SDE'}

#source_properties variable
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly'}

#target_properties variable
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'fort_collins',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': 'gis',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'fort_collins.GIS.PipelineAssembly'}

#after update layer.connectionProperties
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly',
 'workspace_factory': 'SDE'}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Replacing datasource does not work through arcpy

JoeHershman — Sun, 12 Dec 2021 03:19:08 GMT

I notice I did not set the validate parameter to false. I changed this to

layer.updateConnectionProperties(source_properties, target_properties, '', False)‍‍‍

I am now even more convinced replacing database does not work, because this makes the changes but breaks the connection, because it is not possible to update the fully qualified name of the Feature Dataset through this method.

Using this the new output when evaluating the layer.connectionProperties is what was hoped for

{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'fort_collins',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'fort_collins.GIS.PipelineAssembly',
 'workspace_factory': 'SDE'}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Now the dataset is invalid.

I notice a couple things. There is no longer a Database shown in the list after the update. The name of the Feature Dataset is still the old name. However, there is nothing in the connectionProperties that allows one to update the Feature Dataset specifically unless I am not seeing it somewhere.

I am at a loss, I am fully convinced esri did not think of this need but shaking my head if that is the case because to me it seems one of the most useful reasons one would want to change a datasource

Re: Replacing datasource does not work through arcpy

JoeHershman — Thu, 02 May 2019 18:46:33 GMT

Just for yucks I ran the same code on a Feature Class at the root level instead of in a Feature Dataset. In this scenario the the update does work. Still odd because in the properties window the instance setting is inconsistent

In the one that was changed:

When set by adding in standard methods it looks like this where the instance shows the database name, but through code it has the path. I did try to change set the instance to use the database name in the target dictionary but that gave a bad datasource

Re: Replacing datasource does not work through arcpy

SrihariDarapaneni — Thu, 02 May 2019 19:00:00 GMT

There are lot of confusions over names dataset from arcpy's 'connection_info' to desktop ArcGIS Pro layer properties.

arcpy's 'connection_info' dataset means featureclass name but in desktop ArcGIS Pro is different.

only instance, and db_connection_properties in connection_info has to be set properly, as you know, in database and in Arc Pro property there is know value for dataset , if you keep instace, db_connection_properties properly and dataset as featureclass name it will resolve the issue.

and if change feature class name in layer properties then it fine dont worry about other values, still esri has to modify their layer property dialog box.

It is not important to this method where featureclass is whether it is in dataset(Arc Catalog/ArcMap terminolgy) or at root level.

I am successfully changing databases with is method without watching layer property dialog box.

Re: Replacing datasource does not work through arcpy

JoeHershman — Sun, 12 Dec 2021 03:19:11 GMT

If you have this working please post the exact code that works. I have changed to set the dataset to the unqualified name of the dataset as you suggest and the result is the same, only the layer at the top level will change anything in feature dataset does not update correctly.

Your post that shows the json is unclear, it shows setting the database item to FeatureClassName which makes no sense, although I did try just in case. This is not Oracle so there is no instance in the way Oracle uses instance, it is a different database in the same Sql Server 'Instance'

# source
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'Staging',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': '<*********>',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'Staging.GIS.PipelineAssembly',
 'workspace_factory': 'SDE'}

#target
{'connection_info': {'authentication_mode': 'DBMS',
                     'database': 'fort_collins',
                     'db_connection_properties': 'portal07',
                     'dbclient': 'sqlserver',
                     'instance': 'sde:sqlserver:portal07',
                     'password': 'gis',
                     'server': 'portal07',
                     'user': 'gis',
                     'version': 'sde.DEFAULT'},
 'dataset': 'PipelineAssembly',
 'workspace_factory': 'SDE'}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I have run the code replacing everything and also just running with 'database' and 'dataset' being changed. Both have the same result, classes within a Feature Dataset become invalid and it shows the Feature Dataset incorrect. I ran the same code a second time changing the database back and when this is done the datasource becomes valid again (because now the Feature Dataset is correct). I see no way to change the Feature Dataset to an unqualified name so do not know what I am missing

Again, if you have a working sample fo changing the database please post. I am thinking perhaps there is a difference with Oracle and Sql Server but I could just be missing something.

Thanks

Re: Replacing datasource does not work through arcpy

curtvprice — Thu, 02 May 2019 22:44:01 GMT

Have you asked Esri support yet? They can probably explain what workflow you need.

Re: Replacing datasource does not work through arcpy

SrihariDarapaneni — Fri, 03 May 2019 14:54:50 GMT

This sample code i am running sucessfully on oracle db

import arcpy, os, pprint
import traceback
from os import path

project_folder = r'D:\Project\'
project_file = r'sample.aprx'

project_path = os.path.join(project_folder, project_file)
aprx = arcpy.mp.ArcGISProject(project_path)

Source_fc = 'SM.sm__installs'
target_fc = 'SM.sm__installs'

targetInstance = 'sde:oracle$sde:oracle11g:ABCD_P'
targetUser = 'sde'
targetPwd = 'sde123'

for map in aprx.listMaps():
   for layer in map.listLayers():
      if layer.connectionProperties == None:
         continue

   sourceConn = layer.connectionProperties
   targetConn = sourceConn
   print(sourceConn)
   targetConn['dataset'] = target_fc #which is not required if pointing to same fc in other database
   targetConn['connection_info']['instance'] = targetInstance
   targetConn['connection_info']['user'] = targetUser
   targetConn['connection_info']['password'] =targetPwd
   #targetConn['connection_info']['db_connection_properties'] ='xDatabase/xInstance' # this is required for SQL db
   print(targetConn)
   layer.updateConnectionProperties(sourceConn, targetConn)

aprx.save()
del aprx

Re: Replacing datasource does not work through arcpy

JoeHershman — Mon, 06 May 2019 20:58:22 GMT

Thank you for the sample, but this is different from what I am doing. There is a difference in sql server in that it has a database name. This is different from changing an instance, which is what is being done above. Because of how the data connection seems to be maintaining the database name, it is not making the change correctly. If I where only changing the server or instance but keeping the database name the same this issue does not arise. I can change from dbServer01 to dbServer02 as long as the name of the Sql Server database is the same

In Sql Server the identifier is not 'Database/Instance', it is 'Server/Instance' or usually just 'Server' because in most cases the default instance is used which does not have an identifier

Thanks

-Joe

Re: Replacing datasource does not work through arcpy

JoeHershman — Mon, 06 May 2019 21:01:39 GMT

Was hoping to not have to go down that path if possible. But likely the only route, although if it is a bug (or unsupported feature) as I suspect, it is doubtful I would have any resolution within a timeframe that would be useful. Not to mention that amount of time that will need to be spent with tech support repeating everything in this thread with multiple people

Re: Replacing datasource does not work through arcpy

curtvprice — Mon, 06 May 2019 21:24:21 GMT

If you start an incident, be sure and point the tech support people to this thread. In the past that has helped grease the process and save on the back and forth. Also once you have an incident number, they have a record of it and any past and future workarounds or fixes in the database. Please do open an incident, this way others can benefit from your suffering so it isn't wasted!

I have to say I've always been happy with their help, even if it doesn't mean an immediate fix, at least I know of any workarounds right away.

Re: Replacing datasource does not work through arcpy

Anonymous User — Tue, 07 May 2019 14:07:56 GMT

It seems there is a bug in arcpy.mp.updateConnectionProperties where if you are trying to update feature class is in a feature dataset in an Enterprise Geodatabase (.sde) to another EGDB. According to this thread Esri knows about it and will fix in future release (unconfirmed) https://community.esri.com/thread/228083-updating-connection-info-via-python-from-sde-to-file-geodb-with-a-feature-dataset

Re: Replacing datasource does not work through arcpy

JoeHershman — Tue, 07 May 2019 14:20:25 GMT

Thanks.