In another thread a possible workaround was suggested. Use multiple filter instead of “OR” filters and it should be ok. This works fine for exclude filters imo because they can be combined. Include Filters don’t work with this workaround unfortunatley.
This is not helping with multi-conditions, like exclude Device category “desktop” AND Operating system “Linux”.
The crazy thing I am noticing is that now AND works as it is a OR statement, and viceversa. I bet some dev just confused the two before publishing a new version. It tells you a lot about the quality of Google products nowadays.
The number of bugs I experience in GA4 and Looker Studio in the past 6 months is disgraceful.
1 Like
Only solution I can think of is to create a new field for each filter. Essentially, I think you could recreate OR/AND logic through CASE statements that evaluate to TRUE for the data you’d want displayed, and then create a single condition filter on that new field that only displays data when TRUE.
Not really a solution as much as it is a workaround.
It causes issue in aggregated table.
My hackey solution does, or are you saying the bug identified gets in the way of aggregated tables? In either case, how does it cause issues?
Yup - also experiencing this issue! Super annoying
Experiencing the same issue, did it start working for any of you yet?
It looks like the engineering team has pushed out a fix that should take effect on December 17th. Check again then! I’ve also asked support about whether or not we will have to do anything and will update here if I hear anything!
1 Like
Same problem, and is anyone else facing this problem with the pagination in the tables, I go to the next page and when I generate the PDF it generates it from the first page, anyone else having this problem? Or do you know the solution please?
Friend, where can I access these update notices or bug fixes?
I don’t know if you can. I opened a ticket and have been in touch with support so not sure how you’d see that. I’ll update here once I have news though!
1 Like
Thanks WillyGolden for finding out the date of the fix! I checked my dashboards today and the issue seems to be fixed on my end now. I didn’t have to do anything, the red ‘invalid’ message disappeared and the correct ‘Page path’ is back in place on my filters.