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

Simple join between shapefile and table producing no matches upon validation

Mike09

I'm trying to create a join between a shapefile and a table on ArcGIS Pro, but when I tried to validate the join it told me there were no matches. So far I've checked the following common issues:

I confirmed that I had entries in both tables that matched exactly (same spelling, all uppercase, no extra spaces); so I should at least get some matches

I confirmed that they were both the same format (both are text)

I tried different formats for the table (Excel, CSV, DBF)

I made sure the column I was performing a join on had actual values and not an Excel formula

I exported both the shapefile and the table to my geodatabase to try there as well

Does anyone have any other ideas or suggestions for what might be the issue? If I can't get this join to work then I won't be able to use this data in my analysis because it would be far too expensive to geocode a table that large.

Trouver plus de publications taguées avec

Desktop

Accepted answers

All comments

pslgisAdmin

Thank you

I was having issues with a very simple join between a feature class and table in a FGDB. Nothing that I did, no matter where the data was located or stored, ever worked. I made sure that the "Index Joined Field" box and the "Rebuild Join Field Indexes" were both checked, and the Join worked.

Running ArcPro 3.2.2

abaldenweck@blm.gov_BLM_EGIS

I just had to investigate this for something I was doing as well.

This is a quick script I wrote to check what was wrong (I had extra spaces, among other things-- inconsistent abbreviations, etc.)

This might help find the issue?

mp= arcpy.mp.ArcGISProject("CURRENT").activeMap
lay = mp.listLayers("allot")[0] # table one
tbl = mp.listTables("permlist")[0] # table 2
layList = []
tblList = []
# stick in the join fields to each cursor, append to list. 
with arcpy.da.SearchCursor(lay, "ALLOT_NAME") as cursor:
    for row in cursor:
        layList.append(row[0])
with arcpy.da.SearchCursor(tbl, "Allotment_Name") as cursor:
    for row in cursor:
        tblList.append(row[0])
# Get unique values
layList = list(set(layList))
tblList = list(set(tblList))
# subtract each one from the other.
# this made sense in my work flow, since I needed to check
#    if all the values in "lay" were actually represented in
#    "tbl".
# if not, just comment out anything involving notintbl
notintbl = [t for t in layList if t not in tblList]
notinlay = [a for a in tblList if a not in layList]
notintbl.sort()
notinlay.sort()
# print the missing values.
print(notintbl)
print(notinlay)

Eugene_Adkins

A couple different issues. The validation would show "X" amount of returned matches but when the join was applied the attribute table was blank. I contacted tech support and we did tests with a FGDB (instead of my enterprise sourced data) and we also witnessed behavior that returned inaccurate results, though different from the enterprise sourced data. Tech support wanted to do further testing but the case was closed because I did not have time due to the issue preventing me from completing workflows that work normally in 3.1.1.

You can search "join" and "Pro 3.2" on the "ArcGIS Pro Questions" main page and get a couple of returns from others experience varying issues.

Robert LeClair

Is your "Index Joined Fields" check box checked? If so, uncheck and try the join again. There was a BUG-000159354 that was fixed in ArcGIS Pro 3.2 but it has me wondering if it's related.

danretired

Could you show a couple of rows from both tables that should match (a screen grab of both would help)

You said you check for spaces... including trailing spaces?

Mike09

It is 3.2, but I've done other, admittedly much smaller, joins successfully with this version. As part of my troubleshooting I just did a join on a small test table to my layer and it was successful. What issues has 3.2 been having with joins?

Eugene_Adkins

Is the Pro version 3.2? If so, I don't know if this is the first time you've tried creating a join with that version, but I had to revert back to 3.1 because of join issues with 3.2 that prevented me from doing regular workflows.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.