Forum Discussion
Google Analytics connector missing startdate/enddate parameters
We don't do aggregrations locally. All cube operations (Expand, filters, collapse) always results in a query that is 100% sent and run on the service. When you collapse a dimension, we simply don't request it in the query. This is why the date is gone in the second request you've posted. This is equivalent to not selecting a dimension attribute in MDX:
select {[Measure].[Users]} on 0,
filter([Date].[Date].[Date], <date filter>) on 1
from [GA]
Then when the date is collapsed, we issue:
select {[Measure].[Users]} on 0
from (select filter([Date].[Date].[Date], <date filter>) on 1
from [GA])
I tried the same query on our GA account and the issue doesn't reproduce. I get the same results if I aggregate locally using List.Sum over the column than if I collapse the date dimension attribute.
That being said, you seem savvy and I'm sure you've identified something. I'm very interested in getting to the bottom of this and I'll gladly setup a call.
Hi Tristan,
"send a frown" tries to open Outlook, which I don't have. What's the alternative?
If you look at my network traces, you'll observe the flaw in the GA connector. It issues two calls and one of them does include the ga:date dimension, which will obviously result in the wrong answer.
> I tried the same query on our GA account and the issue doesn't reproduce. I get the same results if I aggregate locally using List.Sum over the column than if I collapse the date dimension attribute.
If you get the same answer aggregating locally, then you are reproducing the problem. I am frustrated that you aren't taking the time to read this full discussion thread.