I digged a little deeper. Here is a "run everywhere" demo dashboard. <dashboard version="1.1">
<label>Link Redirect</label>
<row>
<panel>
<table>
<search>
<query>
| makeresults
| eval movie = "Breaking Bad", id = "0903747"
| append [| makeresults | eval movie = "Better Call Saul", id = "3032476"]
| table movie, id
</query>
</search>
<drilldown>
<condition field="movie">
<link target="_blank">http://www.imdb.com/title/tt$row.id$</link>
</condition>
</drilldown>
</table>
</panel>
</row>
</dashboard> Click on the 1. movie. Choose "Don't show this again" and Continue. Now we find the following entry in session storage (Chrome Developer Tools -> Application -> Session Storage): Key: http://www.imdb.com/title/tt0903747 Value: true Logout from Splunk and login in the same tab keeps the data. Closing the tab deletes the entry from the session storage. You get the same problem, if you open a new splunk tab. The entry is missing for this session. From Google Search: "Use the local Storage object if you want some data to be on the browser. If you want it on the server, then use cookies, and the session storage is used when you want to destroy the data whenever that specific tab gets closed" Practically user has to klick "Don't show this again" for every table row, in every browser and for every new tab / session. How can you explain this to the user?
... View more