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
Was the patch released today suppose to address this issue or does it only address the issue with field calculate? I installed the patch today and still see this issue.
Hi Russell,
Do you have a rough timeline of when the patch may be released? It's a pretty important feature for many of our workflows and we don't really have the option of using either of the workarounds unfortunately.
Many Thanks
ArcGIS Pro 3.5.2 patch was released June 24, 2025. ArcGIS Pro 3.5 Patch 2 (3.5.2) Announcement
Thanks, I've updated now and all working again
Experiencing the same
Just an update on this bug...
Bug fixes are addressed in upcoming releases or general patches, or they may be addressed as ad-hoc fixes. Enhancement requests are implemented in upcoming releases.
Updates have been made to the following defect which you are associated with:
BUG-000176615 - In ArcGIS Pro 3.5, related tables for hosted feature layers fail to open when prompted.
Status: Fixed (Learn More)
Version Fixed: 3.6, 3.5.2
Additional Information: This issue is addressed in 3.6, 3.5.2
Alternate Solution:
Work directly with the data stored locally on the machine instead of loading the feature service layer or revert to ArcGIS Pro 3.4.x.
Thank You,
Esri Inc.
THE SCIENCE OF WHERE™
Hi,
Are you able to let me know when 3.5.2 will be released please? I've checked Pro here and it's not yet available.
Thank you,
Karen
Hi Karen - I do not know when 3.5.2 will be released but hopefully soon!
Hello, I experienced this issue with ArcGIS Pro versions 3.5 and 3.5.1, and I've noticed that the new 3.5.2 patch resolves it.