Select to view content in your preferred language

Query Layers or Views don't display popups in New Map Viewer on AGOL or Enterprise

774
3
05-03-2023 09:29 AM
dhaag
by
New Contributor

I have a database view (have attempted with just a query layer as well) that works and has worked in the past to display a custom popup in AGOL and Enterprise.  This layer now won't display the popup in the new map viewer or in dashboards.  If I switch to the Classic map viewer, the popup displays without issue.  Also, if I publish the layer as a hosted service on AGOL it also works fine.  Seems to only be when it is dynamic from our SDE and in the new map viewer.

I've attached 3 images.  popup shows what it looks like in Classic Viewer.  popup2 shows that when configuring it in the new map viewer, it will display, but if you click on any of the points on the map, no popup displays.  poup3 shows a details widget in dashboards showing No Data.

3 Replies
RhettZufelt
MVP Notable Contributor

Your example appears to be point related, so may not apply, but I have had similar issues to this in dashboards using SDE data/views.

Turns out AGOL doesn't play well with fields that are not actually part of the feature class (Shape.STArea(), Shape.STLength()) and are added/calculated on the fly when you access them.

When I modified my view syntax to cast them to a different name, all seems to work fine:

SELECT  OBJECTID, Owner, recnum, Shape.STLength() AS Length

rather than:

SELECT  OBJECTID, Owner, recnum, Shape.STLength()

In fact, I had to create the views in order to overcome this rather than just using the feature class itself.

Hope this helps,

R_

jcokin1
Regular Contributor

It is NOT just points that cause the problems. This is for all geometry types! I have the exact same error with multiple query feature layers (points, lines and polygons) sourcing my SQL server database tables. 

jcokin1_0-1728061317900.png

Due to the complexity of the tables in our RDBMS and the amount data stored (30+ years) in these tables.... they can NOT be exported and reloaded as simple feature layers within an SDE and must reside as SQL server tables hence the use of the Query Feature Layer option

@dhaag  or @RhettZufelt did anyone flag this with ESRI as a bug within Standard Map Viewer? I see the post is almost a year and half old 🤷‍

I have 20+ query feature layers published to portal and no way to access the identify / pop-up results for any of the layers with the new "Standard Map Viewer" vs "Classic Map Viewer"( classic works with pop-ups with query feature layers published to Portal). 

@BernSzukalski and @RussRoberts  ......I am tagging you guys on this as we could use someone from ESRI to see if this bug was ever flagged and has a number or it needs to be cataloged and brought to the AGOL / Portal teams attention. 

I have only come across this community post that talks about the issue. 

 

 

RhettZufelt
MVP Notable Contributor

Only related bug I reported on this was:

BUG-000152780 : In ArcGIS Dashboards, unable to use Shape.STLength() field from a map service in Table and Details elements. "Cannot access data" is shown.

 

R_

0 Kudos