Obsolete
Status Update
No update yet.
Comments
he...@gmail.com
Can't COUNT_DISTINCT() over a specific date range!!! This appears to be a common problem! Please fix ASAP!
he...@gmail.com
Comment has been deleted.
he...@gmail.com
Having the same issue with count distinct when selecting a specific filter
vi...@google.com
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
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
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...
he...@gmail.com
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
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:
ad...@google.com
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
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
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!
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of issue is this? Display or rendering issue
When did this happen?
Dec 10, 2021 15:45 GMT+01:00
What steps would let us observe this issue?
1. Open Telegram.
2. Start a chat.
3. Select a picture or video you would like to send.
4. Select the text field "Add a caption..."
5. Now tap below the tab bar.
What did you expect to happen?
I expected the keyboard (Gboard) to behave normally.
What actually happened?
Gboard turned completely dark or white, depending on whether you had Telegram in dark or light theme.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Slight
Additional comments
This is really really bothering me and I'd love you to fix this asap!
Related apps
Telegram
org.telegram.messenger.web
Version 24969 (8.3.2)
Not system app
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