Issues with Map Tips and Identify - Joins
I have a map service with data that is joined to a table. So, one field looks like {MS_HARV_PUB_POLY.TRT_NAME}. Service is on prem traditional map service.
In the web map and WAB, I have no issues identifying records via map tip. But in the webviewer with AGOL and Portal, I have issues. With AGOL version of web viewer, I get no results when identifying or with map tip. Same service without the join is fine. In webviewer version in Portal, my results in map tip just show the field name like
Treatment Name: {MS_HARV_PUB_POLY.TRT_NAME}
instead of
Treatment Name: My treatment value
Highlighted below: not right. Circled is still correct in the details of map tip. So, really just the header.
In WAB:
-
Sorry, we are in 5.10 of Web in Portal.
0 -
One other note here. Arcade expressions fail in results with a join in WebViewer. They work in the same map service minus the join and also do work in the web map.
0 -
@Pairin Mason? ... I know we fixed a bunch of these issues including support asynchronous Arcade in 5.12. Do you think Ryan's use case is covered?
0 -
@Cam Barnard? , I'm positive that 5.12 changes will cover Ryan's case.
If the issue persists for Ryan, I'd be very interested to inspect to his webmap.
0 -
I am seeing issues in the SaaS world still - actually gives a big error in web traffic. No Arcade expressions used on SaaS web app either. I'll try and upgrade to 5.12 when we get time. Thanks for that info.
0 -
Hi Pairin and Cam - We are on 5.13 GC Web on prem. Seeing much better behavior. However, the header of the pop up works, but only the first time a feature is clicked. Per my screen shots below. The first one shows proper behavior. If I click the same polygon again and every time after, I get the behavior from second screen shot.
missing info:
0 -
Hi Ryan,
I'm unable to reproduce the blank header of the pop up issue mentioned above.
Is the header using a regular field or some special field (i.e. Asynchronous Arcade expression, related field, etc.).
If possible, it would be very helpful if you can share your app and webmap for us to investigate.
Kind Regards,
Pairin
0 -
Hi Pairin - nothing fancy going on, just a table joined to the feature class as layer 0 in the map service. If I choose the same feature class but it is not joined in the same map service as layer 1, there are no issues. I cannot make the app public as it is sensitive data. But, here is the screen cap of map viewer classic. I did open a ticket on this today FYI.
0 -
this is the REST endpoint of the layer schema (snippet)
0
Please sign in to leave a comment.
Comments
9 comments