Question

Results from One Look becoming Filter on Another Look

  • 14 May 2018
  • 1 reply
  • 927 views

Hello,


I have a look that shows recent calls to a single phone number, including call id, call start/end times, call reason, etc.


I want the results of incoming call phone numbers to autopopulate a filter on a separate look on the same dashboard. Is there a way to do this?


Thank you.


1 reply

Userlevel 2

Hi @juberuaga,


Thanks for reaching out. I believe there a few approaches that you could take here, that would need to be adjusted based on the exact requirements of your use case.


The most straightforward approach here would be to create a drill link that you would apply to the field you wish to filter on in the second look. This drill link could link back to the dashboard itself (when the outputted value in the second look is selected), and use liquid variables to pass the original dashboard’s filter values into the URL, and insert the selected value in the first look into the filter applied to the second look. You could also link to another dashboard that is nearly identical to the original, but has the second look (now filtered correctly) included on it.


To do this, we would use the link parameter on the field whose value we wish to insert into the filter that will be applied to the second look. The link doc contains examples of how to ensure that the same filters are passed from the first dashboard to the second, plus the outputted/selected incoming call value inserted into a dashboard filter that will be applied only to that second look. The main drawback to this approach, is that there will need to be an intermediary step of selecting the value from the first look’s output.


The other option to achieve this is a bit more involved. The steps we could take are:



  1. Create a derived table that represents the query underlying your first look. You would need to convert your current dashboard filters (if they exist) into templated filters, and include these templated filters in your derived table sql.

  2. Join the derived table back to the explore

  3. Create a yesno dimension in our derived table view that returns yes when a value from this derived table is returned that meets the necessary conditions to qualify as incoming call phone number.

  4. Use this yesno dimension as a filter on the dashboard, that is applied to the second look (we would set default value = yes).


Please visit us at help.looker.com if you would like to explore either of these options further!


Thanks,


Quinn

Reply