Status Update
Comments
ch...@gmail.com <ch...@gmail.com> #2
ab...@webtmize.com <ab...@webtmize.com> #3
ve...@gmail.com <ve...@gmail.com> #4
em...@gmail.com <em...@gmail.com> #5
Request to Google Data Studio Team to fix this as soon as you can.
ke...@hooplah.com <ke...@hooplah.com> #6
What is the best solution to fix this?
to...@gmail.com <to...@gmail.com> #7
aa...@onimodglobal.com <aa...@onimodglobal.com> #8
bg...@gmail.com <bg...@gmail.com> #9
om...@emojo.co.il <om...@emojo.co.il> #10
au...@brawnmediany.com <au...@brawnmediany.com> #11
pe...@gmail.com <pe...@gmail.com> #12
hf...@hubspot.com <hf...@hubspot.com> #13
[Deleted User] <[Deleted User]> #14
er...@gethunter.com <er...@gethunter.com> #15
bn...@gmail.com <bn...@gmail.com> #16
da...@thisispegasus.co.uk <da...@thisispegasus.co.uk> #17
st...@gmail.com <st...@gmail.com> #18
tl...@gmail.com <tl...@gmail.com> #19
my...@national.aaa.com <my...@national.aaa.com> #20
[Deleted User] <[Deleted User]> #21
bn...@gmail.com <bn...@gmail.com> #22
ma...@gmail.com <ma...@gmail.com> #23
ja...@wmglobal.com <ja...@wmglobal.com> #24
al...@perfectstay.com <al...@perfectstay.com> #25
Any update on the mentionned issue?
This seems crazy to see a simple sum not working....
uw...@ergodirekt.de <uw...@ergodirekt.de> #26
Please fix this issue!
ke...@gmail.com <ke...@gmail.com> #27
Please fix this issue!
ry...@derivesystems.com <ry...@derivesystems.com> #28
an...@oogstonline.nl <an...@oogstonline.nl> #29
lu...@homify.com.br <lu...@homify.com.br> #30
Please fix this issue!
uq...@gmail.com <uq...@gmail.com> #31
rh...@gategroup.com <rh...@gategroup.com> #32
ki...@funnel.io <ki...@funnel.io> #33
em...@funnel.io <em...@funnel.io> #34
to...@trgo.si <to...@trgo.si> #35
ma...@gmail.com <ma...@gmail.com> #36
[Deleted User] <[Deleted User]> #37
[Deleted User] <[Deleted User]> #38
tr...@tijevlam.nl <tr...@tijevlam.nl> #39
tr...@tijevlam.nl <tr...@tijevlam.nl> #40
If you have that filter on the table, it will work but (as said) not on the total. If you add an extra filter-control and add it next to your report (outside the visible page) and set it to a default selection it will work for your total row.
See the image 1 for the setup (i realize now my interface is in dutch, sorry) and image 2 for the proof it works.
te...@google.com <te...@google.com> #41
We released a handful of fixes related to the summary row incorrectly identifying dimensions to drop last month (the last fix was rolled out on Wednesday).
If anyone is still having trouble please share your report with data-studio-help@google.com and I'll take a look.
mp...@google.com <mp...@google.com>
vf...@europcar.com <vf...@europcar.com> #42
pp...@onimodglobal.com <pp...@onimodglobal.com> #43
Summary row math of the columns is off.
[Deleted User] <[Deleted User]> #44
te...@google.com <te...@google.com> #45
Depending on the issues I might need access to the data source as well.
pp...@onimodglobal.com <pp...@onimodglobal.com> #46
te...@google.com <te...@google.com> #47
I think I have an idea of what's going on, but no immediate fix unfortunately.
I added a pair of tables on the second page and it's sending back 4 rows when the table has no dimensions instead of 1 (it should always be 1, since no dimensions means we don't group by any columns).
When Data Studio makes a request for the summary row, we basically just make a duplicate of the normal table request with the dimensions stripped off.
The response is expected to have 1 row, so we just display the first row we get back. The numbers you see are the first row of the request with no dimensions, which in this case is meaningless data.
I'm not sure if this is an issue with the Supermetrics connector or something related to Data Studio not pushing down the dimension filters correctly.
We have a fix for the latter that's going out next week. I can follow up with you on Monday or Tuesday once we're able to narrow it down.
no...@googlemail.com <no...@googlemail.com> #48
Supermetrics describes the issue here:
However they also state it is an issue on Data Studios side.
I will wait and see if the update next week will fix it.
[Deleted User] <[Deleted User]> #49
[Deleted User] <[Deleted User]> #50
ma...@takeflightmarketing.co <ma...@takeflightmarketing.co> #51
fe...@vivi.marketing <fe...@vivi.marketing> #52
ed...@gmail.com <ed...@gmail.com> #53
sy...@skolafund.com <sy...@skolafund.com> #54
ry...@rustandsalt.com <ry...@rustandsalt.com> #55
ri...@rome2rio.com <ri...@rome2rio.com> #56
I'm using a table built on blend of three custom segments using the GA connector.
As a workaround, I switched from the regular table to the Pivot table (with no column dimensions), which appears to calculate the totals correctly.
am...@mgmresorts.com <am...@mgmresorts.com> #57
ma...@ikano.se <ma...@ikano.se> #58
[Deleted User] <[Deleted User]> #59
ka...@makadigital.com <ka...@makadigital.com> #60
an...@launchtitans.com <an...@launchtitans.com> #61
[Deleted User] <[Deleted User]> #62
re...@daviesmeyer.com <re...@daviesmeyer.com> #63
ma...@sitepod.io <ma...@sitepod.io> #64
va...@gmail.com <va...@gmail.com> #65
ja...@pcspecialist.co.uk <ja...@pcspecialist.co.uk> #66
re...@reportdash.com <re...@reportdash.com> #67
Jo...@ProSiebenSat1.com <Jo...@ProSiebenSat1.com> #68
[Deleted User] <[Deleted User]> #69
[Deleted User] <[Deleted User]> #70
Are there any update/ solution how to fix it?
pe...@pmg.com <pe...@pmg.com> #71
[Deleted User] <[Deleted User]> #72
[Deleted User] <[Deleted User]> #73
ro...@gmail.com <ro...@gmail.com> #74
de...@gmail.com <de...@gmail.com> #75
co...@gmail.com <co...@gmail.com> #76
ce...@gmail.com <ce...@gmail.com> #77
ma...@gmail.com <ma...@gmail.com> #78
cm...@digitalangels.com <cm...@digitalangels.com> #79
This problem only happens to me with non-native google data sources. When I tried to ask ReportDash they sent me back to this thread.
Are there any updates about this bug? It's become really impossible.
te...@google.com <te...@google.com> #80
For anyone still seeing this issue with Community Connectors, please see the documentation related to "forFilterOnly" here
The most common cause of this bug is that the response Data Studio gets back for the summary row is incorrectly grouped by a "filter only" dimension, and the summary row response has multiple rows in it. Currently, Data Studio ignores the other rows and just returns the first one. This is not a good way to handle it. We're working on switching it to an error, but we don't want to break too many reports at once so we've been working with connector creators to fix the issue before flipping the switch.
An easy way to confirm if this is the case with your connector is to make two tables:
- The table that is giving you incorrect data (which has a summary row and a filter using a dimension that isn't visible on the table)
- A copy of that table with the same filter, and also with the filtered dimension visible.
If the first row of Table #2 is the same as the summary row of Table #1, there is a bug in the implementation of the AppsScript connector. In this case, contact the connector creator to let them know.
If you are using a Community Connector but don't see the behavior described above, please share your report with
If you are seeing this with a non-Community Connector, please file a new bug so we can track it separately (feel free to link to it here so others can find it).
[Deleted User] <[Deleted User]> #81
da...@anker.com <da...@anker.com> #82
[Deleted User] <[Deleted User]> #83
cl...@gmail.com <cl...@gmail.com> #84
I have attached my updated version of my current role at this point and I hope you will be able to help me with this project as I have been thinking about it for a while now and I think I am going to have a great time with the family and friends with you guys and I will be grateful if you would help us with the new email address I sent you last night and I hope you can help me by this weekend as I have been thinking about it for a while now and I think I am going to have a few people that are coming to the wedding and I think I have a friend who is interested in the opportunity to work with the company I have been so busy with work since I have been thinking about the situation for a while and the fact that I am very excited about the opportunity to be a part of the new team and the company I have worked for the past few years with the team and I have been so busy with the new job at the moment but
ma...@gmail.com <ma...@gmail.com> #85
[Deleted User] <[Deleted User]> #86
ju...@gmail.com <ju...@gmail.com> #87
sa...@x2o.be <sa...@x2o.be> #88
ma...@educations.com <ma...@educations.com> #89
si...@stafferton.co.uk <si...@stafferton.co.uk> #90
me...@merkleinc.com <me...@merkleinc.com> #91
[Deleted User] <[Deleted User]> #92
si...@gmail.com <si...@gmail.com> #93
mo...@numberly.com <mo...@numberly.com> #94
js...@assure-labs.com <js...@assure-labs.com> #95
be...@gmail.com <be...@gmail.com> #96
ll...@fmlogistic.com <ll...@fmlogistic.com> #97
al...@nbiz.com.br <al...@nbiz.com.br> #98
ee...@suez.com <ee...@suez.com> #99
my observation is that:
1) using a plain and simple table to view data from a (mixed) datasource messes up the Totals row.
2) using a table to view data from a mixed datasource WITH AT LEAST ONE filter fixes the problem.
kh...@ada-asia.com <kh...@ada-asia.com> #100
v....@gmail.com <v....@gmail.com> #101
[Deleted User] <[Deleted User]> #102
[Deleted User] <[Deleted User]> #103
[Deleted User] <[Deleted User]> #104
[Deleted User] <[Deleted User]> #105
p_...@hotmail.com <p_...@hotmail.com> #106
ak...@obsidian.dk <ak...@obsidian.dk> #107
ka...@webenertia.com <ka...@webenertia.com> #108
[Deleted User] <[Deleted User]> #109
cb...@gmail.com <cb...@gmail.com> #110
mh...@cpacanada.ca <mh...@cpacanada.ca> #111
[Deleted User] <[Deleted User]> #112
[Deleted User] <[Deleted User]> #113
I'm having this issue even without a secondary dimension or filter. Current workaround is to extract the data to a Google Sheet, where it totals correctly.
em...@unowebdesign.com <em...@unowebdesign.com> #114
[Deleted User] <[Deleted User]> #115
aa...@turner.com <aa...@turner.com> #116
[Deleted User] <[Deleted User]> #117
[Deleted User] <[Deleted User]> #118
pa...@nerveagency.co.uk <pa...@nerveagency.co.uk> #119
[Deleted User] <[Deleted User]> #120
ma...@nomadigital.io <ma...@nomadigital.io> #121
en...@four15digital.com <en...@four15digital.com> #122
cc...@gmail.com <cc...@gmail.com> #123
je...@onlyhumans.com <je...@onlyhumans.com> #124
mi...@360-thinking.co.uk <mi...@360-thinking.co.uk> #125
[Deleted User] <[Deleted User]> #126
[Deleted User] <[Deleted User]> #127
[Deleted User] <[Deleted User]> #128
da...@buyshedsdirect.co.uk <da...@buyshedsdirect.co.uk> #129
ca...@gmail.com <ca...@gmail.com> #130
jo...@den-haan.nl <jo...@den-haan.nl> #131
ge...@fifty-five.com <ge...@fifty-five.com> #132
da...@des.qld.gov.au <da...@des.qld.gov.au> #133
We are considering moving away from Looker studio which appears to be bug ridden and moving to other product like PowerBI or other.
Time series charts also don't display correctly for larger date ranges. Data appears to have stopped halfway through the date range, yet if you use an alternative chart
like a line chart it shows the full data line ok. For us both these issues have started occurring since the cutover to GA4.
These are fundamental basic requirements for reporting.
Description