Trying to update data source for layers in ArcGIS Pro maps programmatically. So, I must be misunderstanding the syntax for doing that explained here. Because the following does not work: import arcpy aprx = arcpy . mp . ArcGISProject ( r 'path to my project file' ) #This gets me list of all the maps maplist = aprx . listMaps ( ) #If I only want those belonging to MyGroup mygroup = aprx . listMaps ( 'MyGroup' ) [ 0 ] #To get the layers in that group grouplayers = mygroup . listLayers ( ) new_sdeConn = r 'path to my SDE connection file' for lyr in grouplayers : old = lyr . connectionProperties #also tried lyr.connectionProperties['connection_info'] lyr . updateConnectionProperties ( old , new_sdeConn ) This doesn't throw an error. it just doesn't do update the data sources as desired. The ESRI example goes like: aprx . updateConnectionProperties ( r 'C:\Projects\YosemiteNP\Vector_Data\Yosemite.gdb' , r 'C:\Projects\YosemiteNP\DBConnections\Server.sde' ) Does this maybe only work for the project as a whole?

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; } } }

Updating Data Source in ArcGIS PRO project with arcpy

Arne_Gelfert

Trying to update data source for layers in ArcGIS Pro maps programmatically. So, I must be misunderstanding the syntax for doing that explained here. Because the following does not work:

<SPAN class="keyword token">import</SPAN> arcpy

aprx <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>mp<SPAN class="punctuation token">.</SPAN>ArcGISProject<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">'path to my project file'</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="comment token">#This gets me list of all the maps</SPAN>
maplist <SPAN class="operator token">=</SPAN> aprx<SPAN class="punctuation token">.</SPAN>listMaps<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="comment token">#If I only want those belonging to MyGroup</SPAN>
mygroup <SPAN class="operator token">=</SPAN> aprx<SPAN class="punctuation token">.</SPAN>listMaps<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'MyGroup'</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN>

<SPAN class="comment token">#To get the layers in that group</SPAN>
grouplayers <SPAN class="operator token">=</SPAN> mygroup<SPAN class="punctuation token">.</SPAN>listLayers<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>

new_sdeConn <SPAN class="operator token">=</SPAN> r<SPAN class="string token">'path to my SDE connection file'</SPAN>

<SPAN class="keyword token">for</SPAN> lyr <SPAN class="keyword token">in</SPAN> grouplayers<SPAN class="punctuation token">:</SPAN>
    old <SPAN class="operator token">=</SPAN> lyr<SPAN class="punctuation token">.</SPAN>connectionProperties	<SPAN class="comment token">#also tried lyr.connectionProperties['connection_info']</SPAN>
    lyr<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>old<SPAN class="punctuation token">,</SPAN> new_sdeConn<SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

This doesn't throw an error. it just doesn't do update the data sources as desired. The ESRI example goes like:

aprx<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">'C:\Projects\YosemiteNP\Vector_Data\Yosemite.gdb'</SPAN><SPAN class="punctuation token">,</SPAN>
                                r<SPAN class="string token">'C:\Projects\YosemiteNP\DBConnections\Server.sde'</SPAN><SPAN class="punctuation token">)</SPAN>‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Does this maybe only work for the project as a whole?

Find more posts tagged with

Accepted answers

All comments

MatthewLeonard

This is the first solution that has worked for me! Good idea, TI...thanks.

JohnGaiot

HOLY COW TI ! Your solution, although a roundabout one, worked pretty slick! I can't believe it's been so hard to find a SIMPLE solution.. Cheers.

RonnieRichards

Thank you for this description. I have been attempting to replace the .sde connections by using the workspace which comes back in describe method. This always appears to be a temporary .sde connection in the user profile for some strange reason. When creating the full path using the temporary .sde workspaces as the current input it never seems to update the data sources.

However your tip led me to the conclusion is we know where already know where all the original sde connection files are used to create the initial map. Using this as the full path+.sde connection file in the current input seems to be working for all of our use cases!

For us this includes different server names, named SQL instances, database name differences, username/pwd. This is even working on query layers from the non-geodatabase SQL databases. In each of these use cases something was challenging when using the find/replace dictionaries in updateConnectionProperties. It worked for some but not others such as the database name differences.

Feel confident we can now proceed with the .sde replacement option! Thanks

StaticK

I dynamically created the full path to the previous sde file in other code, which I use for the input. Maybe it could work with using just the name of the sde file, but since I built out the path using the layer connection_properties, some lyr name mapping, the layer dataset property, and some regex to generate the old path and path to the new connection file and it worked as I needed, I kept it.

RonnieRichards

Interesting. I would be curious what you provide in the current SDE connection input since Pro Maps do not appear to maintain reference to the original .sde connection file. Do you obtain this from Describe or always know the current connection?

StaticK

I found that doing an SDE to SDE change worked for us only if we provide the full path to the new connection file to the connection_info['database'] property- trying to do the dictionary change method or just the 'find replace' name of the connection file bombs.

It would be nice if we could get a success/ fail result from the process instead of it just moving on giving a false positive that it worked. We could print the connection again, but that is ugly.

RonnieRichards

This process is inconsistent for us switching from one SQL SDE source to another. It's a complete mess and used to work just fine in ArcMap/arcpy.

For us if the server name is the only change then the find / replace dictionary works but if anything else is different (database, user, instance) than the find/replace dictionary does not work.

The old / new .sde connection approach has never worked for us

There is a bug in ArcGIS Pro 3.0.3+ if you try to update the WORKSPACE on a map manually it breaks the layers in map document which could be one reason it might not be working consistently with Arcpy.

https://my.esri.com/#/support/bugs/bugs?bugNumber=BUG-000156145

Not sure why they are reporting "as designed" as I would want the workspace option to work like it did in ArcMap. Guess we are asking too much!!

We also created an enhancement because ArcGIS Pro references to the SDE connection properties differently depending on where you look. If they cannot get these properties to be consistent how could any repathing possibly work?

https://my.esri.com/#/support/bugs/bugs?bugNumber=ENH-000161406

ZacharyUhlmann1

I'm just responding here to be updated if this is ever resolved. Perhaps in another 4 years. My code and problem were pretty identical to original post - but moving from one gdb to another gdb with Feature Classes all of the same, exact name. Tried all the solutions offered here in the comments, to no avail.

Honestly not a bad, temporary solution if your situation allows is as follows: 1) Disconnected drive or server containing path needing change 2) Open project 3) Click the red exclamation point from all the broken paths and fix the broken paths. In my case, much of the original data was on a gdb on an external hard drive. If within a Pro project on server 1a) copy it to external hard drive 2a) disconnect from server 3a) fix paths as above 4a) copy back to server / disconnect external hard drive 5a) fix paths again, setting them to desired new gdb. Screw it.

The code snippet below is part of my Python tool which makes this easy.

In my code, this is run within a loop for multiple layers and it very slow, as it has to wait for ArcGIS Pro to add each layer to the map and then remove it again. ArcGIS Pro is the most unresponsive application I've used on any OS anywhere anytime ever (can you tell it annoys me? A lot.).

Before this snippet, the logic gets a list of all featutre classes in the new Data Source and for each of the old feature classes to be changed, it checks the list to make sure that there is one with a matching name in the new Data Source to use as 'fcNew'. If there is not, then my particular tool will output a warning, and depending on another parameter in the tool, may also remove the layer if its data source could not be updated (due to no matching FC in the new DS).

        fcNew = os.path.join(newDS, fcName)
        tmpLayer = map.addDataFromPath(fcNew)
        newProperties = tmpLayer.connectionProperties
        map.removeLayer(tmpLayer)
##        arcpy.AddMessage("OLD connection properties:\n{}".format(layer.connectionProperties))
        layer.updateConnectionProperties(layer.connectionProperties, newProperties)
##        arcpy.AddMessage("NEW connection properties:\n{}".format(layer.connectionProperties))

diaconori

Could you please share your implementation? It does sound like a good, hacky approach but it'd be nice to see it with some actual code.

Thanks.

I went for the full-on sledge-hammer approach. Here's what worked for me:

Add a NEW TEMPORARY layer to the map from the equivalent feature class in the new data source (using some matching of names logic from the feature class of the old layer)
Get the connection properties of this temporary layer (into a Python variable)
Remove the new temporary layer from the map
Replace the connection properties of the original layer with the connection properties of the (removed) temporary layer

yay! it works at last!

Anonymous User

Old thread, but seems to get a lot of traffic and thought I'd add a solution that worked for me. Needing to update paths from shapefiles to a GDB, I think that the ESRI documenation for replacing parts of the path string is assuming that it is still a GDB to GDB update, like all of their other examples. Their provided example syntax failed to update the paths so after some digging I came up with creating the connection property, which worked:

lyrcon = {'dataset': lyr.name, 'workspace_factory': 'File Geodatabase', 'connection_info': {'database': newDataPath}}

lyr.updateConnectionProperties('', lyrcon)

diaconori

I can also confirm that this does not work in 2021.

I've implemented various variations of the solutions proposed on the posts related to this issue, and to conlcude things, none of them works.

EDIT:

Only way to do this is to go the ArcMap route. ConnectionProperties is just over-engineered and too complex to work with. Use lyr.findAndReplaceDataSource and you'll accomplish this in no time.

BinhLe

Jeff,

I used this script and nothing happened. I went into Catalog View to try and change the sde connection path and it won't save. I can find and replace it, but when I hit apply, it would revert back to the old one.

JeffMoulds

Starting at ArcGIS version 2.6, we improved this workflow so that you can use Enterprise Geodatabase Connection Files in the first parameter of the UpdateConnectionProperties function. You can now do something like the following code sample.

<SPAN class="keyword token">import</SPAN> arcpy 
aprx <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>mp<SPAN class="punctuation token">.</SPAN>ArcGISProject<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">'C:\Projects\YosemiteNP\Yosemite.aprx'</SPAN><SPAN class="punctuation token">)</SPAN>
aprx<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>r<SPAN class="string token">'C:\Projects\YosemiteNP\DBConnections\TestGDB.sde'</SPAN><SPAN class="punctuation token">,</SPAN>
                                r<SPAN class="string token">'C:\Projects\YosemiteNP\DBConnections\ProductionGDB.sde'</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

You can also call updateConnectionProperties on the project, map, layer, table or LayerFile.

More info and code samples can be found here: Updating and fixing data sources—ArcGIS Pro | Documentation

Anonymous User

I've contemplated going the ArcMap route as well. Hopefully, I can avoid that, but...

Arne_Gelfert

Folks, I was reminded of this thread when stumbling across a similar one - here. Turns out that while I would've preferred to be able to update references from one SDE connection file (with embedded credentials) to another and do so programmatically, simply running an update on [user] and [password] was the quickest.

conProp <SPAN class="operator token">=</SPAN> layer<SPAN class="punctuation token">.</SPAN>connectionProperties

<SPAN class="comment token">#depending on what all you're updating, you may have additional</SPAN>
<SPAN class="comment token">#keys you need to address</SPAN>
<SPAN class="comment token">#Examples: https://pro.arcgis.com/en/pro-app/arcpy/mapping/updatingandfixingdatasources.htm</SPAN>

conProp<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'connection_info'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">'user'</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> newuser
conProp<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'connection_info'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">'password'</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> newpassword

layer<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>layer<SPAN class="punctuation token">.</SPAN>connectionProperties<SPAN class="punctuation token">,</SPAN> conProp<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

AlbertoAloe

Hi everybody.

I run into this post and I realized that I may have something simple but useful.

The script below just goes layer by layer in a chosen map within the 'CURRENT' project and update user and password on sqlserver sde layers.

It is meant to be used within a script tool (pass the password as 'hidden string' data type). The logic excludes group and basemap layers and checks the data source in the connectionProperties looking for data source hints in the dictionary (I just look for SQL Server). The try/except block catches NameError exception for other layers

<SPAN class="keyword token">import</SPAN> arcpy
<SPAN class="comment token"># Input parameters are  the chosen map within the current project, new user name and password</SPAN>
mapName <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>GetParameterAsText<SPAN class="punctuation token">(</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">)</SPAN>
newUser <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>GetParameterAsText<SPAN class="punctuation token">(</SPAN><SPAN class="number token">1</SPAN><SPAN class="punctuation token">)</SPAN>
newUserPass <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>GetParameter<SPAN class="punctuation token">(</SPAN><SPAN class="number token">2</SPAN><SPAN class="punctuation token">)</SPAN> 
<SPAN class="comment token">#===================================</SPAN>
<SPAN class="comment token">#The default project is the current one....</SPAN>
aprx <SPAN class="operator token">=</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>mp<SPAN class="punctuation token">.</SPAN>ArcGISProject<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'CURRENT'</SPAN><SPAN class="punctuation token">)</SPAN>
currentMap <SPAN class="operator token">=</SPAN> aprx<SPAN class="punctuation token">.</SPAN>listMaps<SPAN class="punctuation token">(</SPAN>mapName<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN>

<SPAN class="comment token">#Loop layers excluding group layers and basemap</SPAN>
<SPAN class="keyword token">for</SPAN> lyr <SPAN class="keyword token">in</SPAN> currentMap<SPAN class="punctuation token">.</SPAN>listLayers<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN>
    <SPAN class="keyword token">if</SPAN> <SPAN class="operator token">not</SPAN><SPAN class="punctuation token">(</SPAN>lyr<SPAN class="punctuation token">.</SPAN>isGroupLayer <SPAN class="operator token">or</SPAN> lyr<SPAN class="punctuation token">.</SPAN>isBasemapLayer<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="comment token">#I have to exclude group layers and basemaps of course.....</SPAN>
        <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
            <SPAN class="keyword token">if</SPAN> lyr<SPAN class="punctuation token">.</SPAN>dataSource<SPAN class="punctuation token">.</SPAN>split<SPAN class="punctuation token">(</SPAN><SPAN class="string token">','</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">2</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">.</SPAN>split<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'='</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">1</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">==</SPAN> <SPAN class="string token">'SQL Server'</SPAN><SPAN class="punctuation token">:</SPAN> <SPAN class="comment token"># basically if the layer has a sql server data source</SPAN>
                new_conn_prop <SPAN class="operator token">=</SPAN> lyr<SPAN class="punctuation token">.</SPAN>connectionProperties
                new_conn_prop<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'connection_info'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">'user'</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> newUser
                new_conn_prop<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'connection_info'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">'password'</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> newUserPass
                <SPAN class="comment token"># Now i can update the connection properties dictionary of the layer</SPAN>
                lyr<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>lyr<SPAN class="punctuation token">.</SPAN>connectionProperties<SPAN class="punctuation token">,</SPAN>new_conn_prop<SPAN class="punctuation token">)</SPAN>
                arcpy<SPAN class="punctuation token">.</SPAN>AddMessage<SPAN class="punctuation token">(</SPAN>lyr<SPAN class="punctuation token">.</SPAN>name <SPAN class="operator token">+</SPAN> <SPAN class="string token">' has been updated !'</SPAN><SPAN class="punctuation token">)</SPAN>

        <SPAN class="keyword token">except</SPAN> NameError<SPAN class="punctuation token">:</SPAN>
            arcpy<SPAN class="punctuation token">.</SPAN>AddMessage<SPAN class="punctuation token">(</SPAN>lyr<SPAN class="punctuation token">.</SPAN>name <SPAN class="operator token">+</SPAN> <SPAN class="string token">' does not have  a sql server data source'</SPAN><SPAN class="punctuation token">)</SPAN>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

I hope this helps

Alberto

TobiSellekaerts

Just one. But within this one project there are 35 layers to be repathed. I will exhaust many attempts at automation before changing them all manually!

mvolz47

Tobi:

I have not tried to recreate my update SDE datasource scripts from ArcMap to Pro yet so I have not experienced this hardship yet, but I have found that the Set Data Source(s)... functionality of ArcCatalog has not been ported over to Pro. Although this ArcCatalog functionality does not work on batch mxds, I have found it very useful for moving publishing mxds from development to test to production where the SDE database is different for each environment.

How many Pro aprxs are you looking to update the SDE connection properties for?

Set Data Sources Tool in Pro

Arne_Gelfert

As with so many other instances, not finding any info on how to do it, I abandoned this a while back. But I'm sure I will have to look at it again some day and will remember this post.

TobiSellekaerts

Sadly I have given up banging my head against the desk trying to make this work. I have searched through three other threads on GeoNet of people having a variation of this same problem without resolution:

updateConnectionProperties

ArcPy Layer updateConnectionProperties not working as expected

Replacing datasource does not work through arcpy

and elsewhere:

Repoint enterprise geodatabase connection using ArcPy in ArcGIS Pro - Geographic Information Systems Stack Exchange

In the end I found an old ArcMap .mxd with the same data also pointing to the wrong database, used good ole reliable lyr.replaceDataSource() to fix the data sources, imported the mxd as a new map in Pro, then copied the data over into my original map. Sad but true.

BrettLessner_Nsight

Has anyone solved this? I'm trying to move a workflow from Map to Pro, and this is hanging me up. It was so much easier with the lyr.replaceDataSource().

StephenM

Hm, maybe the credentials can't be modified in the way the other values can. I do notice that there aren't examples in the documentation that show changing users in the connection properties. I had some success changing a connection from an OS authentication connection to a DBMS connection, but I don't have multiple named DB users to test changing credentials.

Arne_Gelfert

I've tried passing in a complete new dict or just the 'user' and 'password' values as you suggested. I've tried the approach of referencing another layer's connectionProperties suggested here:

lyr <SPAN class="operator token">=</SPAN> m<SPAN class="punctuation token">.</SPAN>listLayers<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'some other layer'</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN>
l<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>l<SPAN class="punctuation token">.</SPAN>connectionProperties<SPAN class="punctuation token">,</SPAN> lyr<SPAN class="punctuation token">.</SPAN>connectionProperties<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

None of it is working. Darn!

StephenM

Ah, right. I forgot that you're using SDE connections. To switch users I'd try modifying ['connection_info]['user'] and ['connection_info']['password'].

<SPAN class="keyword token">for</SPAN> lyr <SPAN class="keyword token">in</SPAN> layers<SPAN class="punctuation token">:</SPAN>
    old_conn <SPAN class="operator token">=</SPAN> lyr<SPAN class="punctuation token">.</SPAN>connectionProperties
    new_conn <SPAN class="operator token">=</SPAN> old_conn
    new_conn<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'connection_info'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">'user'</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> new_user
    new_conn<SPAN class="punctuation token">[</SPAN><SPAN class="string token">'connection_info'</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">[</SPAN><SPAN class="string token">'password'</SPAN><SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> new_pw
    lyr<SPAN class="punctuation token">.</SPAN>updateConnectionProperties<SPAN class="punctuation token">(</SPAN>old_conn<SPAN class="punctuation token">,</SPAN> new_conn<SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Arne_Gelfert

Stephen, thanks. Appreciate you chiming. I realize that connection_info is a dictionary. But I wasn't sure how to use it. Keyword "database' only updates the database. I'm actually trying to switch this to use a different account (new 'user' and 'password') and was hoping to do so using a new SDE connection file. Can you maybe not to do?

If you look at the other keys in the dict, I need more than 'database' to be updated.

{'authentication_mode': 'DBMS',
 'database': 'Prod',
 'dbclient': 'sqlserver',
 'db_connection_properties': 'myserver',
 'password': '<*********>',
 'instance': 'sde:sqlserver:myserver',
 'server': 'myserver',
 'user': 'myaccount',
 'version': 'dbo.DEFAULT'}

I am not an expert on these SDE connection files. But my understanding has always been that they store a reference to DB server/instance, DB name, authentication (and/pr password). So basically what's in the dictionary above. So merely updating 'database' in the dict wouldn't be sufficient, I think. To be safe, I tried it, and to no effect.

StephenM

The issue you're having is that lyr.connectionProperties returns a dictionary but your new connection is a workspace path. You just need to access the right key in the dictionary:

<SPAN class="" style="color: #0077aa; border: 0px; font-weight: inherit; font-size: 14px;">for</SPAN> lyr <SPAN class="" style="color: #0077aa; border: 0px; font-weight: inherit; font-size: 14px;">in</SPAN> grouplayers<SPAN class="" style="color: #999999; border: 0px; font-weight: inherit; font-size: 14px;">:</SPAN>
&nbsp;&nbsp;&nbsp; old <SPAN class="" style="color: #a67f59; background: rgba(255, 255, 255, 0.5); border: 0px; font-weight: inherit; font-size: 14px;">=</SPAN> lyr<SPAN class="" style="color: #999999; border: 0px; font-weight: inherit; font-size: 14px;">.</SPAN>connectionProperties['connection_info']['database']
&nbsp;&nbsp;&nbsp; lyr<SPAN class="" style="color: #999999; border: 0px; font-weight: inherit; font-size: 14px;">.</SPAN>updateConnectionProperties<SPAN class="" style="color: #999999; border: 0px; font-weight: inherit; font-size: 14px;">(</SPAN>old<SPAN class="" style="color: #999999; border: 0px; font-weight: inherit; font-size: 14px;">,</SPAN> new_sdeConn<SPAN class="" style="color: #999999; border: 0px; font-weight: inherit; font-size: 14px;">)</SPAN>

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.