Join not working

[AvaFarouche]

Hi, all,

I'm working in Pro 3.4.3. I'm trying to create a join between a layer and a Standalone Table - which is something I've done countless times with no problem. As background, the original layer file I'm working with was a .gpkg. I exported it to a layer file and I hoped that would solve my problem because I was then able to create an attribute index for it.

It sort of worked, in that I didn't get any errors and I could see the new fields from the Standalone Table were added to the table for my new layer, i.e., the tables did join. But none of the values carried over. All of the values in fields from the Standalone Table are <Null>. Every single one.

The layer and the standalone table each have a field "PWSID" that I used for the join. While there may be some errors or records that don't match, there are many that do. I spot checked and can find matching numbers in the two tables. So it's not a matter or the join records not matching. There should be at least some records that have value. But there are none.

Any ideas?

Thank you!!

[DanPatterson]

Add Join (Data Management)—ArcGIS Pro | Documentation

Join Field (Data Management)—ArcGIS Pro | Documentation

get the tables and featureclasses in a locally stored file geodatabase as a first test of the data

the latter is for permanent joins, so I would go with the first as a start.

If the data and join all checks out, then you can assess what might be the issue with the data in its current form

[RTPL_AU]

Not to be silly but have you tried to turn it off and back on again?

I have torn out my hair with Joins in Pro and sometimes it just doesn't want to play ball.

Close Pro and restart the machine. Except for the cases where I messed up spectacularly this has fixed most of my Join issues where you can compare the two datasets and are 99.9% sure things should work.

In very few cases I've had data that looks 'just right' but will not join in Pro. The same data when copied to Excel and thrown to a vlookup works 100% so there is something that can break that will cause a Join to fail.
I've then done the export/import to a different FGDB or to csv & back to 'clean out' data. 

Let us know what you find.