BUG-000146306 for ArcGIS Pro

Bug ID Number	BUG-000146306
Submitted	January 24, 2022
Last Modified	June 9, 2026
Applies to	ArcGIS Pro
Version found	2.9.1
Operating System	Windows OS
Operating System Version	10.0 64 Bit
Status	Known Limit

Additional Information

This is a known limit with CSV files, where the feature class attribute table and the CSV file are looking at two different data type columns. When creating a CSV file, if a single integer is added, it is treated as an integer. The attribute table field that is used, such as a text field, does not match the CSV field even though they both have an integer value. This is why the CodeNum field works, because both now have a matching data type for the integer value. If the match table is created with the same setup in a geodatabase, with the Code column set to text, both data types match, and it works as expected. If the CSV file is opened in Excel, it illustrates what is happening here. If the match table is created with two columns, such as 'Code' and 'Filename', and 1 is entered, the value is on the right side of the cell, such as an integer value. If a new row is added and is typed as 1A, this value is on the left side of the cell as a text value, which is why it works with number or text combinations. Another workaround is also added as an option to create the match table in the geodatabase and not in a third-party format, where controlling the behaviour is beyond the scope of ArcGIS.

Workaround

Create a new field of an Integer data type, and copy the records from the Text field to the new Integer field.
Set the Integer field as an Input Join Field. The tool runs successfully with the images attached.

Consider creating the table in the geodatabase where the field data types are specifically set.