So we finally upgraded to the latest version of the explorer app on iOS (v.17.1.2 of app running on iOS 10.3.3), serving up maps from our Portal for ArcGIS instance through a VPN to the device. One of the things we were keen to make use of (and part of the reason for the upgrade) was the related records capability, of which we have quite a few. However, when I interrogate those map layers containing related records I do not see them. Are there any specific requirements for this to work, or has anyone else come across similar issues?
Solved! Go to Solution.
Hey Dan,
I worked with Mervyn on this issue we found a few bugs with related records (as well as a bonus issue) -- here are the results:
Can you mark this as the correct answer?
Thanks,
Joel
Hi Joel,
I've marked this as the correct answer (the second bug), although it is a bug rather than our problem being solved. Unfortunately we can't export the layer with the definition query and republish as this would significantly alter the architecture of our data model.
Thanks Dan!
Marking my response as the correct answer will allow other users to determine if this is the same issue that they are running into. Once I get the official BUG numbers from support I will edit my response above to include them. This will make it easier for other users who want to be attached to the BUGs in order to track developments progress.
I understand the workarounds are not ideal, but I wanted to include them in case someone needs to get around this bug asap. We are well aware of the issues and are working diligently to get them addressed!
Joel, we are having the same issue with Explorer. Our example is one point feature class related to another point feature class. In this case it is streetlights related to a Work Request with a GPS location. Popups for both feature classes work in Portal, however users cannot click on a light and see the related work requests. We would prefer to not symbolize the work request and have users access them through the light as a related record.
Explorer version 17.1.2
Portal 10.5.1
ArcSDE 10.2.1
Published using ArcMap 10.2.1 (as a map service only, not a feature service)
PK/FK has been turned on, the other two workarounds are not an option for us.
No definition queries defined in the publishing map.
Hey Robert Harris,
There is a known issue where the related data will not be returned if the Map Service is added to the map by the map service root url. Can you try adding the streetlights and work request layers to a map by the map service layer (ie "https://.../MapServer/4" & "https://.../MapServer/5") to verify this is the issue you're running into?
Thank you Joel. Technically that does resolve the issue. I am able to view related tables in popups by adding the map service layer. I need to do some more testing to see the overall impact of this for our production mapping environment. In our most used web application (and Explorer map) we have a map with 7 map services feeding the map, and up to 41 layers in each map service...
I can see how that would be a pain. Hopefully we can get this addressed in an upcoming release. Depending on how you have your map set up you may be able to cherry pick the layers that you add individually. In other words, add the Map Service by the root url -> remove the layers that have related data -> Re-add the layers with related data individually. This may not be a viable option for you, but worth pointing out.
Working through that now. Any grouping we had configured in the map is gone at this point. For example, our users like to turn on 'electric' layers as a group, but would now have to know to go back and turn on the lights and work requests as well. To have to do this for everything we use related tables for would just not work for us.
I think I understand ESRI's reasoning here, if there is a GPS location, just click on the point to see the attributes of it directly, right? From our perspective, we collect several inspections per asset per year. We want to use a point feature class to easily symbolize for the crews when an inspection has been completed. For our office users, it would be difficult to guess at which 'inspection' they would need to click on to see the series of inspections. (Think 20 or so inspections for each asset over a couple years). We've toyed with the idea of collecting the points with GPS, then extracting the data to flat tables which should allow us to display related records in a web map. There is significant overhead involved with this so we haven't proceeded with it yet. Think doing this for pole inspections, light repairs, manhole inspections, gas valve inspections, water valve inspections, gas riser inspections, bar code tracking gas assets, gas leaks, water leaks, any attached images, etc...
This is definitely considered a bug and not as intended or designed. You should be able to access your related records from the Map Service layer without taking extra steps. With that said, I certainly understand how the workarounds will not suffice for most users. I'm hoping we can get this addressed in one of our updates following 18.1.0.
The issue of related records not showing up is also true for Collector.