Select to view content in your preferred language

Map Viewer Does Not Render Points from 1:M Joined Table in ArcGIS Online

310
3
02-24-2026 10:31 AM
TFLAHR
by
New Contributor

Hi Everyone,

In ArcGIS Online, I am trying to create a Joined View Layer (with admin privileges) from a point feature layer and table that have a one-to-many relationship class which was created in ArcGIS Pro using a GlobalID and GUID field (I used the Inspection Workflows video as reference). Once created, I published the layer and table to AGOL.

In the screenshot below is my relationship class structure.

RCS.png

However, when I create a Joined View Layer using the parameters in the screenshot below, I cannot see the records that I created in the related table on the Map, as they should be represented as points. However, when I open the attribute table I can see those test records, but when I try to zoom-to nothing happens.

HVL.png

I have done this exact process in the past with no issues (using a GlobalID and GUID). I have tried republishing, updating extents, creating indexes for the GUID, and tried the Join Features tool in Mapviewer and Mapviewer Classic with no success.

Has anyone had this problem before?

Thank you!

 

0 Kudos
3 Replies
EmilyGeo
Esri Regular Contributor

Hi @TFLAHR

Thanks for sharing your workflow and the steps you’ve tried. I haven’t encountered this issue before.

Is there a reason you need to both join and relate these datasets? Depending on your goal, a relate alone might achieve what you need. 

Could you elaborate on what you’d like to do with this data in Map Viewer? That will help us determine whether a join is necessary or if another approach might work better. 

Best, Emily

0 Kudos
TFLAHR
by
New Contributor

Thank you for the quick response! 

This project is for recycling audits within our region. Since the contractor who will be performing the audits knows the area well, and will be attaching multiple records throughout the year to property addresses, I thought that using Survey123 connect to collect information would be the most effective solution.

In terms of data structure, I created a one-to-many relationship so that multiple audit records can be attached to single address points. And furthermore, I wanted to create a joined view layer so symbology in a dashboard can be driven based on audit results. 

I did find some potential workarounds where you can use arcade expressions to drive the symbology without the need for a joined view, but it sounded a bit too cumbersome.

0 Kudos
EmilyGeo
Esri Regular Contributor

Hi @TFLAHR

Thanks for explaining your end goal. Styling the layer based on the audit records could be tricky with that structure, especially since multiple records could be tied to a single point. 

If you’re able to share the layer, we can take a closer look to see what’s happening. 

Best, Emily

0 Kudos