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

Join Field Not Working

LeviCecil

I've been having this problem lately, where the join field tool won't work in Pro 2.6 or 2.7, or Python 3.7.9. I'll try to join on two fields that I know are identical, and it will say "WARNING 003237: Join had no matches." Is anyone else having this trouble? When I run the same script in Python 2.7, the fields join. This happens whether I'm trying to join a csv to a feature class, fc to fc, or a gdb table to fc.

Finde mehr Beiträge mit dem Tag

Desktop

Accepted answers

All comments

DanPatterson

What does the Validate Join (Data Management)—ArcGIS Pro | Documentation

tool show?

What are the contents of the fields?

pure text or numeric as text?

any potential leading/trailing spaces in one of the table fields?

left vs right justified "numbers"? (first is text, second is probably a number)

Mary_Murphy

Are you trying to join to a .csv or other excel table?

LeviCecil

I got "WARNING 003237: Join had no matches" from validate join.

LeviCecil

This happens whether I'm trying to join a csv to a feature class, fc to fc, or a gdb table to fc. Whatever I'm trying to join the table to, it doesn't work. There are a couple of null values in the key field, but that shouldn't matter, should it?

DanPatterson

It does matter. The only way to limit the problems are to use TableToTable or ExcelToTable to bring tabular data into Pro first prior to trying a join. Nulls or any variant of missing data can convert numeric fields to text. Tabular data also may contain leading trailing spaces which need to be properly parsed. A trailing space won't be visible to you but will invalidate a join. If you know there are nulls in the key field, you need to exclude those records at source. There are other variants/issues that I haven't covered here, but in short... if the data are not pristine in the source or target tables, then complete or partial failed joins are the result.

LeviCecil

I do use table to table in my script to convert the csv into a geodatabase table. This is the input for the join fields tool. It still gets thrown by the nulls. It’s not a problem when I run the script in Python 2. What do you recommend as a solution? There is always the possibility of nulls with the amount of data I’m converting.

LeviCecil

Joining is still a problem in Pro 2.8

SGuiryVR

I get the same issue, even though I performed calculate field based on a .csv table based on an ID # value, then when I remove join and try to join again based on the calculated field it says the join had no matches

Spatialelement

Has this issue been resolved? I'm currently trying to perform a very simple join in ArcGIS Pro V2.9.0 and am getting the same "WARNING 003237: Join had no matches". This warning ID doesn't seem to appear in any help documentation other than this thread.

I've checked the raw data for any blank values etc. I've indexed my join fields. I've converted my incoming CSV to a table stored in my projects default geodatabase. Nothing seems to be working.

skyhook

also suffering from this bug. same as described above. taken all previously mentioned steps & attempting to join 2 file geodatabase tables. Shortly before tool finishes it's run I see "0 matches" & i get NULL output. However, history & processing details just show operation succeeded with no warnings or errors. This is a huge disruption in workflow. reminds me of the common joke: funny how arcmap is more useful than ever before now that it's end-of-life & not updated any longer.

shan_sarkar

That is definitely weird, however can you check if there are any extra spaces before or at the end of the fields you are trying to join. If there are extra spaces in the values then arcgis will fail to see them as the same or identical values as it compares the values character by character.

Arsen_Beglaryan

***UPDATE***

I have done some tests today shortening paths etc. and that was not the issue. The cause of this was one row manually selected and forgotten in my 1200 row input table. For that reason the Join Field GP tool was returning no matches. It started working properly as soon as I unselected the row in the input table, no queries were applied. Working on ArcGIS Pro 2.9.1

Any updates on the issue?
It is already becoming a bit "not funny" at all. Having the same issue on 2.9, losing tons of time having to perform this simple task on an ArcMap, QGIS or other tools.
It works one time and keeps on failing other times in ArcGIS Pro with same parameters, either Warning 003237 or tool finding 1 match only.
I have no nulls, spaces etc., having a "table to table" table in the default GDB, that already worked one time and kept on failing other times with same parameters.

Only other potential solution I am thinking of, is the long path issue on Windows machines. I had this type of weird errors in other GP tools that got solved shortening the names and paths etc., but did not try in this case.

LeviCecil

Here's a fun new wrinkle in Pro 2.9.1. Lately I've been successfully joining from Excel sheets. The other day I added new fields to a Sites points dataset and calculated values from an Excel sheet using the Site ID field as the join. I found out this morning that the Site ID field in around 45 of our sites was deleted during this process. They were nulls. This messed up the functionality of our facilities dashboard app. I had to go in and add the Site IDs back in. This is a real problem.

JosephAlberts

I was just running into this problem myself on Pro 2.9.2.

Basic steps were Table to Geodatabase from CSVs prepared for me, attempt join from a hosted feature layer added to the map to the new table. I was joining from the GlobalID of the hosted feature layer (type: GlobalID) to the GlobalID in the table (type: string, length: 255).

If I reversed the join (i.e, table to hosted feature layer, same join field), everything was fine.

It seems like my problem, in this case, was that I had a definition query applied to the hosted feature layer. When I turned it off, I was able to get a correct match count when validating the join from the hosted feature layer to the table.

That's definitely not the behavior I would expect though.

ColinHLang

I have been seeing this recently in ArcGIS Pro 2.9.7. Two tables will not join, especially when the join field is a text field. I can visibly see the matches, but the software can't find them. No leading or trailing zeros or spaces. Some null records, so that is one thing I'll have to investigate, but I've also found I have better results often after I index the field on both sides of the join. Why it would fail without an index and succeed with it is vexing me. I would expect it to just take longer, not fail completely. Joins definitely work a lot better in ArcMap than they do in Pro, and that should not be the case. This is some of the most basic functionality of GIS.

Kalgul

I have aged about 10 years in the past few workdays, spending about 15 man-hours trying to get past this ONE problem which has completely stopped my workflow in a career-defining project. Selecting by attribute confirms the matching entries for a 1:M join, but it just will not join, no matter what I do. I have the shapefile, I have the csv, I have both of them exported to a geodatabase, and nothing I do has gotten past the cursed 'WARNING 003237: Join had no matches.' error.

LeviCecil

If you have access to the Data Interoperability extension for Pro, I would highly recommending using it for joins and attribute management in general. It's basically a lite version of Safe FME software, which is basically a really advanced version of model builder. It does these sorts of tasks so much better than ArcGIS Pro. I'm moving some of my processes out of Python/ArcPy into FME and it's very effective.

Kalgul

I spoke with Colorado State University's Geospatial Centroid, and they instantly found the issue. I was trying to Join a Text(12) field with a Double field, which are incompatible. The issue instantly went away when I created a new Text(12) field and applied the contents of the old Double field into the values with the Calculate Field utility, using a simple Arcade script.

Text($feature.ID, '000000000000')

ID was the name of the old Double Field to pull from, and there are 12 zeroes to match the 12-digit text string. There was a hitch at first, because I had an active selection. Once I cleared that, the calculation went without a hitch, validation instantly worked with the Join function, and now it's Joined.

'WARNING 003237: Join had no matches.' is a completely inadequate error code. ArcGIS Pro should 100% state "Warning, you are attempting to join incompatible field types. Please ensure you are joining identical or compatible fields."

JMCM

Firstly, if you're joining hosted feature classes, make the join layer non-hosted by exporting it. If you have a .csv or Excel file, export it into a table.

Secondly, make sure your field types are the same: double to double, text to text.

I've had issues in ArcGIS Pro even when all this was accounted for. In my latest case, my key was a set of numbers converted to text, but the fields wouldn't match keys properly until I added a letter at the end (e.g. the letter "a" to both keys; obviously the same letter to both). No other changes to the field. I'm not sure why.

Finally, try exiting and restarting Pro.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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