[Maps] Tooltip filter option using "is one of" operator #87864
Labels
[Deprecated-Use Team:Presentation]Team:Geo
Former Team Label for Geo Team. Now use Team:Presentation
enhancement
New value added to drive a business result
Describe the feature:
At this moment it is only possible to add filters, by clicking on the little plus-sign behind a field (inside the tooltip which shows up after clicking a point on the map), for boolean, text and integer values. It would be great if there is an option for array or comma separated values as well, using the "is one of" operator instead of the "is" operator. See this link as example of a map, I am talking about.
Describe a specific use case for the feature:
The documents displayed on the map contain each an array with id's of related documents, which are stored in a separate index. By clicking on a document on the map, I would like to filter on the values of that array, so the other visualizations in the dashboard can show information about the related documents from the other index.
For example: I have one index with a bunch of geographical data points, I have merged all points which are like 100 meters apart from each other and saved the merged documents (which will contain only one central geographical data point), with an array containing the id's of the original documents, in a separate index. The map only shows the merged documents, but by filtering on one point, I would like to filter on the array values (containing the id's of the original documents), so the other visualisations can show the original data.
One alternative would be to give the merged documents and related documents (from the other index) some key with unique id as value, so I could just use the textual filter option. But that would mean I have to update all documents in both indices. And I guess an option to filter on an array would be so much more helpful. Besides, it already works if I just add a filter with the "is one of" operator and copy/paste the values manually, so guess this is more of a front-end feature as it is back-end
The text was updated successfully, but these errors were encountered: