Would you be able to clarify "one" in this sentence - "what if that field you joined has more than one". It sounds like you might have to concatenate the two fields before and create a unique identifier.

@SpatialZone so I have a field called groveid in a feature layer and one in a standalone table, I want them to grab the matching one and give me the field labeled blk from the standalone that being said there is more than one matching groveid in the table and only brings over one in using your tutorial above

@@jodib9598 So you join "groveid" from your feature class and from your "standalone table". Basically, you'll create a new column in the feature class, and transfer the values from "blk" from the standalone table. But the problem, it sounds like you have more than one record in the standalone table (1:M relationship). For example, you might have in the feature class A1. Then, you might have in the standalone table multiple A1s. Is this correct? If I understand this correctly, this means that for every instance there is an A1 in the standalone table... then, you'd want there to be a record to be created in the feature class. So if you have 5 A1s in the standalone table, this means 5 overlapping points in the feature class. If I interpreted this correctly, I've had to do this in the past in ArcMap (not ArcGIS Pro). Follow the same steps as above. But try exporting it as a new feature class. I remember in ArcMap that the resulting feature class would have multiple points overlapping for each associated record in the standalone table. More information about cardinality and 1:M relationships here - gisgeography.com/relate-vs-join-attribute-tables-arcgis/

@SpatialZone thanks, I have done the one to many relate .