morningfoki.blogg.se - Esri make query table tool 10.5

#Esri make query table tool 10.5 update#

The map document was not corrupted and all the layers used the same credential to read from a Sql server SDE database.Īfter spending some time googling, I found some people were struggling over the same issue and suggesting removing/replacing formerly join features is a solution. A ‘item with the same path name already exists’ error message appears when I switched to the Package Map tool. Recently I encountered the ‘general function failure’ message while running the share as map package tool.

The versions of ArcMap and ArcGIS Pro I used in the testing are 10.6.1 and 2.2.4 respectively.

Then use the new table in the rest of the steps. Instead of creating a Table View, exporting the table to another table with the same where clause. Solution? It is easy enough to get a workaround. It seems it get the where clause from the Add Join tool but does not remove it while the join is dropped. The whereClause of the layer is not None. I used arcpy.da.Describe() to inspect the layer and eventually found the issue. The issue happens after remove join obviously.

Select all by using Select Layer by Attribute, where clause “1=1”.

Join the feature layer to the table view, join type is KEEP_COMMON.

Creating a feature layer using Make Feature layer tool without any where clause applied.

Creating a table view using Make Table View tool with where clause.

My logic was simple in the script as presented in the following. I then manually repeated the procedure in ArcGIS Pro and found the same error happened after Remove Join during opening the attributes table of the layer. However, in my case, although there was a join, it was later dropped before Copy Feature. Most of the answers from google were about invalid field names in SQL expression, which means there is at least one join on the source layer. The script raises ‘An expected field was not found or retrieved properly’ while running Copy Features tool.

#Esri make query table tool 10.5 update#

I was expecting a smooth update by simply running the 2to3 tool. Recently I found an interesting issue while upgrading some of the ArcGIS Desktop arcpy scripts to ArcGIS Pro.