Not all records in CSV file could be joined to the feature class in ArcGIS pro

[GeorgeJonesRIGOV]

Number of records in CSVRecords from join in Pro

Hi all, the total number of records i have in my CSV file could not be joined to my feature class I have in ArcPro. Even I noticed the records in the field I have in ArcGIS Pro have the exact same text value as their counterparts in the csv file. For instance, only 140 of 352 could be joined. What am I doing wrong? Thanks!

[AustinAverill]

Is this a local feature layer or hosted? I have experienced non-sense issues like this before with Hosted layers where it just does like half the join and then quits.

[RichardDaniels]

What Field are you joining on? Matches have to be exact so even an extra space within a text field would make a difference (i.e., 'this' is not equal to 'this '). One option would be to do the import table command in Pro then join that vs. using a .csv directly. 

[BarryNorthey]

I suggest that you explore the Add Join Help Usage section. It explains the various conditions that impact how Add Join operates. For example, CSV files do not have an Object-ID field, which can affect how they work as opposed to tables with an ObjectID field. Exporting the csv to a fGDB table creates a new table with an ObjectID field and exporting it to the same fGDB workspace as the input table creates the conditions for a one-to-many join.

Also from the Help: One-to-first joins are not case sensitive; one-to-many joins are case sensitive.

As noted elsewhere, text field values can have invisible trailing spaces. These can be stripped (Arcade Trim or Python Strip) on tables with an ObjectID field.