Latest Contributions by MKF62

**Edit** - I have since closed my python script and reopened it. Now when I run it, I get the error "Cannot open workspace" when edit = arcpy.da.Editor(arcpy.env.workspace) is called. I imagine this is because the SDE database is not versioned, so I have set edit.startEditing('False', 'True') and also tried edit.startEditing('False', 'False') however that does not solve the problem either. I have a script that takes data from a shapefile (using a search cursor) and copies it to a SDE feature class (using an insert cursor after some data manipulation). Obviously, the shapefile is in a different workspace than the SDE feature class. I've read that this error occurs because you need to do your nested cursor actions in an edit session, but that does not seem to solve my problem. I don't think this has anything to do with registering layers with the SDE database as the feature class was created inside the SDE database using ArcMap, therefore it shouldn't need to be registered (right? My knowledge on registering things is limited). It's not versioned and will not be in the future as there is no need. Here's the main portion of the script: #Set the workspace to access feature classes in the HbMonitoringTest SDE database arcpy.env.workspace = r'C:\Users\user\AppData\Roaming\ESRI\Desktop10.5\ArcCatalog\myServer_HbMonitoringTest.sde' #Getting feature class from database PatchesFC = "Patches" #Get input shapefile from different workspace InputFC = r'C:\Users\user\Desktop\GIS_Testing\HbtatTesting\ExpTestFC.shp' #create fields variables and a few other things here #Start editing session on the SDE database edit = arcpy.da.Editor(arcpy.env.workspace) edit.startEditing() edit.startOperation() with arcpy.da.SearchCursor(InputFC, scFields) as sCursor: #Search cursor acts on shapefile        for row in sCursor:         rowList = list(row)         PatchID = '{' + str(uuid.uuid4()).upper() + '}'         ObserverID = None         rowList.insert(2, PatchID)         rowList.append(ObserverID)         rowTuple = tuple(rowList)         with arcpy.da.InsertCursor(PatchesFC, icFields) as iCursor: #Insert cursor acts on SDE database             iCursor.insertRow(rowTuple) #Stop editing session edit.stopOperation() edit.stopEditing('True') ... View more

So, I understand that GUID fields aren't supported by shapefiles, and when you do a join manually in ArcMap (right click layer in TOC > join), it converts the GUID field to a string to join a table with a GUID to a shapefile. I figured it would do the same thing in arcpy as it does in ArcMap when using JoinField_management, but instead the tool fails. Is there any way to have that GUID field convert to string so I can join it with my shapefile? The only way I can think to do it is to copy the SDE database and change the GUID field to string field before joining it with my shapefile in arcpy, but I really want to avoid doing that as it isn't practical. ... View more

I copied and pasted a feature class from one enterprise geodatabase to another. In the catalog window, the naming scheme shows up correctly for the new database, but when I add the layer to the map, the naming scheme changes to the old database. New database is called FocalAreasTest1, old database is called FocalAreas. It only appears to affect the feature classes I copied over and not the tables. Any idea why this might be happening and how to fix it? The source looks correct, it's just the name in the TOC. New database in catalog window naming scheme (FocalAreasTest1): Added MonitoringPoint feature class to the TOC, along with a table that I also copied from old database to new using the same procedures as the feature classes, notice how they are both children of a single parent database (the new one): Source window for the newly added MonitoringPoint feature class where it looks to come from the correct source: ... View more