Why point features in a query zoom to location, but polygon features don't?

[SimonCrutchley]

This is sort of a continuation of this thread (https://community.esri.com/t5/arcgis-enterprise-portal-questions/how-to-get-a-query-result-to-symbol...), so I'm hoping to get an answer. When I run a query on the two layers within my app, I get different responses in the results. In both cases I've set up so that the results show results using the webmap settings, which results in a filmstrip with a thumbnail image and some text. If I click inside any example of one of my point feature results, the map zooms to that location. However, if I try to do the same for the polygon features nothing happens. I can't use the 'Data Actions' option, which might allow this, because it enables Export of data (even when this is unticked) and I cannot allow this.

People were very helpful getting me to be able to change the query result appearance, so I'm hoping you might have an answer here.

Thanks

[Laura]

I can easily zoom to a result from a query on a polygon feature. There's no need to use the data action; instead, you should use the message action. When the record selection changes, it will automatically zoom to the selected feature when you select that option. 

[SimonCrutchley]

Unfortunately, that's what I've already got, and it works fine for the points (obliques), just not the polygons (verticals).

Any thoughts?

[Laura]

Have you tried a separate query widget with those configurations for just the polygon layer to see if a configuration issue or something else?

When you click on map, zoom to does the trigger data have all data selected?

[SimonCrutchley]

No, I hadn't thought of that. I'll give that a go tomorrow as it's home time here in the UK.

Thanks

[SimonCrutchley]

Okay... I tried setting the verticals as a new query and it worked fine. I then added the obliques and hey presto, that didn't. This suggests that the zoom functionality only works for the first element in the query.

I guess I can do a workaround by creating a button with the two queries in it, so it looks seamless to a user, but it seems rather odd and annoying.

[Laura]

I can get it to work with both point and polygons within the same query widget though. Definitely weird behavior.