Hi everyone!
Im facing an issue in Looker that I'm not sure if its an expected behaviour or maybe a small bug: if you try to add in the filters an advanced logic (like after 90 days ago and before 2 days ago), Looker automatically creates it in a new AND filter group (see screenshot), but the issue is that when you schedule this from a Look, in the settings of the schedule that filter of date doesn't appear. Indeed I have done some testings and it seems that the schedule only shows the first level of the AND. Have you faced a similar situation? Could it be a bug? Thanks in advance🙂
In the shedule the advanced filter doesnt appear os its not applied:
Thanks in advance
Solved! Go to Solution.
It seems that it does not show those filters, but it does apply them, based on a test I just did there. But there is clearly a gap there in letting the user know what is going on. Let me see if I can follow up with the Product team on this. Thanks for bringing it to our attention!
Edit: I just checked - it seems the Product team is indeed aware of this behaviour already.
Thanks for flagging this. I notice that, when saving a Look like this to the dashboard, we get a notification as we see below, stating that 'filters using 'OR' will not be displayed on the dashboard, but I can see from the result set that they have been applied correctly. I wonder if this is a case of a missing message, rather than a bug? If you test the actual data in the scheduled Look, is it correct?
Hi,
Thank you for the answer. In my case I dont see that message since Im not using an OR filter, only ANDs:
And the results in the look are correct, the generated SQL too. The issue is that when I try to shedule that Look, those filters of the second AND dont appear there, therefore I cannot shedule the Look with those filters applied, how could we solve it?
Thank you!
It seems that it does not show those filters, but it does apply them, based on a test I just did there. But there is clearly a gap there in letting the user know what is going on. Let me see if I can follow up with the Product team on this. Thanks for bringing it to our attention!
Edit: I just checked - it seems the Product team is indeed aware of this behaviour already.