I have been asked by my water meter department to create a join for our customers meter information. The join will connect to the towns parcel layer using the map and lot numbers for each parcel served. I have been able to do a one to one join with no issues at all but when it comes to a one - many join I'm not making the connection for some reason I'm obviously missing something but I cant figure it out. We have a handful of parcels that have several meter accounts under one map and lot so I'm hoping someone can point me in the right direction to get this fixed. The Parcel Layer and the customer meter table are both inside the same File Geodatabase.
I also want to get this join to be viewed in ArcGIS online as well.
Thanks for any help in advance,
Todd
Add Join (Data Management)—ArcGIS Pro | Documentation
Is this the tool you are trying to use?
Thank you.
Hi @ToddHill
This could be a terminology thing but it sounds to me as if a Relationship Class-based dataset would be your best go, especially if you want to use it in AGOL as well. ArcGIS Pro 'Joins' only exist in the map you have open (simplistically put). You mention FGDB so SQL Views are not an option.
In a Relationship Class Your Property polygon will be the primary / origin item and then the various meter accounts/records can be in a table related to the property. This gives the 1-Many relationship you're after
.
The Relationship Class members can be uploaded/published to AGOL and used in a variety of ways.
There are still some glitches in the Matrix Map so 'obvious' things like popups in Online maps & apps have caveats. With Arcade you can do some cool things too; while pulling out your hair.
Note:
If your tables & features are already in a hardcore production environment with dependencies that must not be broken, take some time before adding Relationship Classes.
Thank you for the information unfortunately I'm still struggling with the one to many join it shouldn't be that hard to get this to work but I'm not seeing what it could be on my end.
I’ve dealt with similar one-to-many join challenges in ArcGIS. What worked for me was exporting the related table to a summary view or using relationship classes instead of standard joins. For reporting or analysis, I often switch to using “Relate” or even script-based solutions in Python for more control. ArcGIS Pro handles some of this better, but it's still tricky.
I'll check it out.
Thanks for the tip.