Assigned
Status Update
No update yet.
Comments
in...@nolimitsoftware.co.uk
Can't COUNT_DISTINCT() over a specific date range!!! This appears to be a common problem! Please fix ASAP!
jo...@google.com
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.
ch...@gmail.com
Having the same issue with count distinct when selecting a specific filter
cs...@arista.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.
ad...@ozbeanz.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.
ch...@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...
zj...@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.
jo...@google.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:
ch...@gmail.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.
ch...@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)).
je...@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!
we...@troop33.org
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.
in...@nolimitsoftware.co.uk
Same problem here. Count_distinct(column) fails when multiple values of a filter is applied.
Very Critical for us.
Very Critical for us.
in...@nolimitsoftware.co.uk
It's incredible given how debilitating this is, how long this bug has existed 😢
ch...@gmail.com
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
lo...@gmail.com
Comment has been deleted.
jm...@ggl.guyg.fr
I'm having the same issue, reading from a CSV and unable to count_distinct() a text field. Somehow this is fixed if I blend the data
ch...@gmail.com
Same here. Postgres connector. count_distinct() returns the value as if it were grouped by day and then summed, rather than a true distinct count for the duration of the date range selected
ma...@kemmer.team
Same issue here...csv file, when a data range is selected, them returns incorrect value
ra...@gmail.com
same here. Mysql connector. Data range filter + count distinct >> wrong value
ch...@gmail.com
Same issue. We solved by combining the data with itself, but it's a very dirty solution. Wait for a real fix !!
I also try using directly a calculated field with COUNT_DISTINCT() but it gave the same wrong result.
I also try using directly a calculated field with COUNT_DISTINCT() but it gave the same wrong result.
ch...@gmail.com
This has nothing to do with connetors or anything.
The problem is probably that COUNT_DISTINCT get's executed before the filter and afterwards the filtered values get aggregated together (mostly summed). It's a real Deal breaker ...
The problem is probably that COUNT_DISTINCT get's executed before the filter and afterwards the filtered values get aggregated together (mostly summed). It's a real Deal breaker ...
is...@google.com
bl...@google.com
Same issue here, from postgres connector. I would really appreciate if some time was allocated to fix this issue.
da...@motorolasolutions.com
Same here. Postgres connector. count_distinct() returns the value as if it were grouped by day and then summed, rather than a true distinct count for the duration of the date range selected
ak...@malone.edu
It fails when dimension is a date and metric is CTD. I use mysql connector and experiencing same issue.
[Deleted User] <[Deleted User]>
+1 It fails when dimension is a date and metric is CTD. I use mysql connector and experiencing same issue.
Tr...@myfitnesspal.com
+1 same problem here wtih PostgreSQL connector.
ch...@gmail.com
+ 1 same problem here with CTD and PostgreSQL
jp...@google.com
We are also facing this issue, especially when doing a roll-up to year-week. Funny thing is, in some cases it works and in other cases not.
I even get different results on two different data sources while both of them use the same custom query.
I can not put my finger on where the difference is.
EDIT 1:
I was able to get arround the issue by adding
CAST(DATE_FORMAT(date, '%Y%u') AS CHAR) AS year_week
to the query. Using this as a dimension works fine.
EDIT 2:
After having added filter controls to the page, the described workarround ceased to work on that page. On another page that uses the same data source, it still works however.
The next strange thing is, that with my described workarround I still get correct numbers in a pivot table visualisation but not with stacked column chart visualisation. It becomes even more weird as I already successfully applied my workarround to another stacked column visualisation.
I am baffled and this issue is indeed a huge annoyance.
I even get different results on two different data sources while both of them use the same custom query.
I can not put my finger on where the difference is.
EDIT 1:
I was able to get arround the issue by adding
CAST(DATE_FORMAT(date, '%Y%u') AS CHAR) AS year_week
to the query. Using this as a dimension works fine.
EDIT 2:
After having added filter controls to the page, the described workarround ceased to work on that page. On another page that uses the same data source, it still works however.
The next strange thing is, that with my described workarround I still get correct numbers in a pivot table visualisation but not with stacked column chart visualisation. It becomes even more weird as I already successfully applied my workarround to another stacked column visualisation.
I am baffled and this issue is indeed a huge annoyance.
da...@motorolasolutions.com
It seems to be the number of filters applied which causes a problem.
[Deleted User] <[Deleted User]>
I seem to be having this issue with a csv upload. Data studio sums up the field as opposed to counting unique accounts. This is only an issue when multiple drop downs are selected from the filter. It works as it should at total level or with one filter selected.
in...@nolimitsoftware.co.uk
Same issue, distinct count is not working on applying the date range filter. However, it populates correct result without any filter.
jo...@gmail.com
Same here.
ch...@gmail.com
+1
[Deleted User] <[Deleted User]>
+1
jo...@gmail.com
+.1 I have noticed count distinct displaying incorrect numbers after a filter has been selected, and decided it's best to stop using it until a fix has been implemented properly.
in...@nolimitsoftware.co.uk
Comment has been deleted.
ka...@gmail.com
I spend so much time for nothing because of this bug, unbeliveable!
ch...@gmail.com
What is the status on this?
Description
First, please search through existing issues to ensure that the feature request has not already been reported. You can start the search here:
If the feature has already been requested, you can click the star next to the issue number to subscribe and receive updates. We prioritize responding to the issues with the most stars. You can also comment on the issue to provide any context of how the feature would benefit you.
Also, please verify that the functionality you are requesting is not already present in the current API and tools.
If your feature has not been requested, please provide all of the following:
-----------------------------------------------------------------------------------------------------------------------------
A short description of the request:
There is still no API access for Google Sites, we really need to have API access to develop tools for users to speed up Site creation and management.
What is the purpose of this new feature?
Give developers the opportunity to let users work on sites projects, perhaps saving features and sharing across site projects. Allowing more design control offline which can then be published uploaded.
What existing APIs would this affect?
Sites API, Drive possibly
What existing data does this use?
Currently is on for Classic Sites, and not working due to the migration to new sites.
Please provide any additional information below.