I am in the testing stages for a potential project and want to use related tables in AGOL pretty aggressively. My goal is to save on having to have a bunch of fields for contact information for contractors by using related tables. What I have right now is 5 contractor fields in the parent table for users to enter in a contractor name for a plumbing, electric, and general contractors that will then be the key to relating to a singular contractor table. In that child table, data for all contractors will be stored. The Contractor name is the relation key that I used to related each of my 5 contractor fields to the contractor table. I created these relationships in ArcGIS Pro and published to AGOL. When I make a pop-up for the parent feature to the user can see the related item for each field AGOL sometimes grabs one relation and put in the pop-up for all other relations. You can see that is the pop-up screenshot below. AGOL returns the wrong item for different relationships. This is a problem like 80% of the time, the other 20% it works as it should and returns the actual item that is related. So long story short I have 5 fields in a parent feature class that are all related to a singular field and I have problems with pop-ups returning wrong items. Is there a fix to this or this a true limitation?
