nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Relate" Bug with ArcGIS Pro 3.5

DJB

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

Find more posts tagged with

Accepted answers

All comments

Robert_LeClair

@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.

JasonDzurisin1

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.

Richard Howe

Can confirm I also see this bug

RussellBrennan

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

DJB

I just spoke to Esri Support today. Just waiting on their analysis and confirmation of a bug.

I'll update this post if or when I receive a reference #.

DJB

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.

Richard Howe

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 🙄

RussellBrennan

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.

RyanTucker

Experiencing the same

KadinBaird41

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.

codethemap

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?

DJB

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™

KarenDrummond

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

Robert_LeClair

Hi Karen - I do not know when 3.5.2 will be released but hopefully soon!

ChristopherDawe

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

Robert_LeClair

ArcGIS Pro 3.5.2 patch was released June 24, 2025. ArcGIS Pro 3.5 Patch 2 (3.5.2) Announcement

ChristopherDawe

Thanks, I've updated now and all working again

JohnHernandez

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.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.