I just upgraded to ArcGIS Pro 3.5 yesterday (05/13/2025) and found a bug that is a bit of a pain.
All of my feature services in ArcGIS Online (AGOL), which have published relationships, do not relate properly in 3.5. I open the attribute table, select a record and click on relate and nothing happens. Any feature classes that I have locally, all those relates work perfectly.
So to test this, I uninstalled 3.5 and reinstalled 3.4 and all of my AGOL relates work perfectly.
I just wanted to post this bug just in case you are considering migrating to 3.5 and you do rely on doing AGOL relates.
~DJB
@DJB - I highly recommend that you contact Esri Support Services to create a case file and possible bug report with that team. If they can replicate it this workflow as you did, then they will create a bug for this item and fix it in a future update.
I've spent nearly a week now trying to figure out what I was suddenly doing wrong. Happenstance lead me to this goose chase but just asked a colleague with 3.3 to try it and it works fine. Hoping for a hotfix very soon.
Can confirm I also see this bug
Hi all, have any of you submitted a support case? If you have a case number you can share I can reach out to the Support analyst directly.
Can you confirm these are the steps to reproduce:
1. Add an AGOL feature service layer/table (layer 1) and it's related layer/table (layer 2) to a map in Pro.
2. Open the attribute table for layer 1.
3. From the attribute table window click on the 'burger' and then select 'Related Data' > layer 2
4. This should select the related record in the map for layer 2 and open layer 2's attribute table with the related record selected. Bug> step 3 doesn't do anything.
Edit: this seems to be feature services in general not specific to AGOL based feature services
I added a hosted (AGOL) feature service to ArcGIS Pro, which has a published relationship. I select a record and click on relate and nothing happens. No related record is selected and the attribute table doesn't even open. Nothing happens. It's like ArcGIS Pro does not recognize that there is a relationship present.
I received correspondence back from ESRI UK this morning that this has been acknowledged and logged as:
BUG-000176615
The two workarounds suggested aren't particularly useful:
1. Download the data to a local geodatabase if you wish to interact with it like this
2. Uninstall 3.5 and reinstall 3.4 🙄
If relate not working in 3.5, does it mean it neither work for python toolbox which uses relationship classes to fetch the related data?
Thanks for bringing this to our attention and apologies that we missed this in our internal testing. We have been able to reproduce this in house and are currently working on a fix. Barring any unforeseen problems or compatibility issues, we are planning to have this fixed in a Pro 3.5 patch.