Hello, recently a lot of co-workers have expressed that whenever they delete their filters to change to a new filter the old filter that they deleted will repopulate itself when they delete a second filter.
(It kind of looks like you’re playing whack-a-mole with filters.)
Has anyone experienced this before and know a fix for it?
This all makes perfect sense now.
conditionally_filter:in the model file re:
Hello Mike, I sent pulls a little while back and they said they could see the whack-a-mole behavior happening and that they’d send it to the Eng’s. I haven’t heard anything back as of yet. Have you happened to see or hear anything on this?
conditionally_filterset as follows —
— if there’s a filter in place on the dimension
foo(and no others) and the user removes that filter to instead filter on the dimension
baz, then the filter on
foowill repopulate itself when the filter on
bazis removed. This sounds like what you’re describing and is by design. Obviously, Looker staff will be able to help you personally and determine whether that’s the issue in your case, but hopefully this post will help others who run into the same issue.
We are looking into this. Can you send URLs or Looks of where this is being experienced to help.looker.com