Obsolete
Status Update
Comments
he...@gmail.com <he...@gmail.com> #2
Can't COUNT_DISTINCT() over a specific date range!!! This appears to be a common problem! Please fix ASAP!
at...@google.com <at...@google.com>
at...@google.com <at...@google.com> #3
Instead of counting unique values in a specified column COUNT_DISCTINCT counts rows in a database (on a view, not a table, to be more specific)... It works as expected with spreadsheets.
he...@gmail.com <he...@gmail.com> #4
Having the same issue with count distinct when selecting a specific filter
he...@gmail.com <he...@gmail.com> #5
From my side, I'm using Postgres Database (All good in Postgres doing the same grouping-unique, so no issues in DB or in Data).
If no values are selected in Filter Control widget the COUNT_DISTINCT is working as expected as it's getting Unique values for the entire dataset, but when I put a value in Filter Control, COUNT_DISTINCT is generating a wrong value.
If no values are selected in Filter Control widget the COUNT_DISTINCT is working as expected as it's getting Unique values for the entire dataset, but when I put a value in Filter Control, COUNT_DISTINCT is generating a wrong value.
he...@gmail.com <he...@gmail.com> #6
I've run into the same issue. I'm connected to Postgres. When I apply a date filter to any metrics that use COUNT DISTINCT, the results wind up being COUNTs.
he...@gmail.com <he...@gmail.com> #7
I can't believe that Google has left this bug unresolved for months, this is a joke. Any time we apply date filtering, and try to utilise count distinct aggregation, when we apply further filtering through other dimensions, the metrics become extremely overstated.
Please sort this out Google, we will have to move to a different tool as this is fundamental functionality...
Please sort this out Google, we will have to move to a different tool as this is fundamental functionality...
ps...@google.com <ps...@google.com>
at...@google.com <at...@google.com> #8
My read on this is that Google doesn't care about Postgres/Redshift support for GDS, and that anyone not on BigQuery should choose a different BI tool. It's really unfortunate because GDS seemed to have a lot of potential.
he...@gmail.com <he...@gmail.com> #9
We're using Big Query and have similar issue, don't know how long we have
to wait to get this resolved.
On Tue, Feb 4, 2020 at 1:02 PM <buganizer-system@google.com> wrote:
to wait to get this resolved.
On Tue, Feb 4, 2020 at 1:02 PM <buganizer-system@google.com> wrote:
he...@gmail.com <he...@gmail.com> #10
Yeah, I don't think this is connector specific. It more so seems like a bug in how Data Studio handles count distinct aggregation when applying a date range and in conjunction with filtering with other dimensions. I created another thread for this here: https://issuetracker.google.com/issues/148813902
Feel free to jump in on it and comment as well, this bug is affecting us massively here.
Feel free to jump in on it and comment as well, this bug is affecting us massively here.
he...@gmail.com <he...@gmail.com> #11
On our side it's probably working with a view vs actual table. Funny enough same data with the same filters displays in expected number of rows (so it can distinguish between unique entries properly (same string)).
he...@gmail.com <he...@gmail.com> #12
Interesting. I am using Postgres and I gave your idea a shot, but a view and a table result in the same bug. However, I also tested to load the exact same data source onto Google Sheets and then load it onto Data Studio and the problem was resolved. So I was wrong^^ it IS connector specific. I guess the guy above^ is probably right. I'm pretty sure Google is aware of this but doubt they will ever fix it.
Best case if any one stumbles upon this 1) Either use a proxy like GSheets to load your data on there first if you are experiencing this bug with MySQL or Postgres or whatever other engine, or 2) Switch to a different BI tool!
Best case if any one stumbles upon this 1) Either use a proxy like GSheets to load your data on there first if you are experiencing this bug with MySQL or Postgres or whatever other engine, or 2) Switch to a different BI tool!
sa...@google.com <sa...@google.com>
he...@gmail.com <he...@gmail.com> #13
Using Redshift with the Postgresql connector. When I render the individual values as a table, everything is correct, but when I render a COUNT DISTINCT in a score card I get incorrect numbers similar to what has been described above. We've really liked Data Studio so far as a BI Tool but it's a serious bullet if it can't do such a basic counting function correctly. The worst thing to present in a business report is data that is obviously wrong.
pa...@google.com <pa...@google.com> #14
Same problem here. Count_distinct(column) fails when multiple values of a filter is applied.
Very Critical for us.
Very Critical for us.
he...@gmail.com <he...@gmail.com> #15
It's incredible given how debilitating this is, how long this bug has existed 😢
pa...@google.com <pa...@google.com> #16
Same problem on Postgres, please get this fixed, it GROUP BY on the date range dimension field so it's unable to COUNT DISTINCT properly
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? User Interface, Display, or Rendering issue
When did this happen?
Dec 13, 2021 13:26 GMT+01:00
What steps would let us observe this issue?
1. Open Settings > Developer Options > Animator duration scale and switch to 1.5x (to see it easier).
2. Use light theme (to see it even easier) and open an app.
3. Minimize the app via gesture navigation and directly afterwards swipe down on the emerging home screen to get to the notification shade. You might need a few tries to reproduce this. (Look into the video to know the exact timing. It also took me a few tries)
What did you expect to happen?
I expected the notification shade to show immediately and smoothly.
What actually happened?
The notification shade appeared immediately, but there was some weird pop-up flicker from the minimized app.
How often has this happened?
Occasionally
What was the effect of this issue on your device usage, such as lost time or work?
None - device worked normally
Additional comments
I wasn't able to capture the bug with the native screen recording tool that's built-in to Android 12L. I recommend you to optimise it in future versions! It's very laggy while recording!
Debugging information
Google Play services
com.google.android.gms
Version 214218053 (21.42.18 (190400-410302452))
System App (Updated)
Android System WebView
com.google.android.webview
Version 466409233 (96.0.4664.92)
System App (Updated)
Network operator: Vodafone
SIM operator: Vodafone
Filed by Android Beta Feedback. Version (Updated): 2.22-betterbug.external_20211027_RC01
To learn more about our feedback process, please visit