Status Update
Comments
[Deleted User] <[Deleted User]> #3
ma...@crediblemind.com <ma...@crediblemind.com> #4
ma...@justeattakeaway.com <ma...@justeattakeaway.com> #5
cr...@papertrail.io <cr...@papertrail.io> #6
mp...@connexion.tv <mp...@connexion.tv> #7
mp...@connexion.tv <mp...@connexion.tv> #8
Since we can't assign the date range control a value from the url, we need to send the parameter of start and end date to each of the datasource added to the report because we can't re-use the same URL param for each datasource we are getting so close to the 2048 limits this is scary.
- datetimestart = 49char
- datetimeend = 49char
- timezone = 38char
- speicifiid = 64char
total 200 char that is for each datasource in addition to the report url. The url looks quite ridiculous with the same field repeated multipletime
di...@gmail.com <di...@gmail.com> #9
The bizarre thing here is, Data Studio already supports using one input box control to enter the value of a parameter, which then auto-magically applies to all data sources. Yet, the URL is not accepting the same syntax. Given that, there's another (incomplete) workaround here that involves serving the Data Studio iframe over a reverse proxy, which in turn enables programmatic entry of the parameter value into the off-screen control boxes via JavaScript. However, this solution is incomplete since it breaks some of the CORS requests made by the embedded page (affecting styles).
I'm not sure how the single-input-box control is implemented that it applies to all data sources, but clearly that's already working - we just need to trigger this existing logic from the URL.
mp...@connexion.tv <mp...@connexion.tv> #10
When you said that, I thought, maybe there was a way to simply use the url param to send a value to the input box that is assigned to a parameters... Because I also saw the behavior you described, but never thought anything about it.
To get the inputbox Id, I activated the feature "Enable view filters in report link". Then I added a inputbox assigned to a dimension. Then I copied the url, pasted it and entered a value in the input box. In Edit mode, in the inputbox, I changed the dimension to a paramters. Then I tried the url Again
No luck, it does not want to pass it to the parameters...
About the fact that you can enter a parameter in 1 input box and it magically populate the other box really seems to the same behavior as the filters If you have ds1 with a field name "color", but you apply this filter to ds2 where it has the same field name (the filter will first look for the same id, then match the name if possible). It really feels like the parameters are acting the same.
The fact that we could have assigned the inputbox a value, but it's not accepted because it's a parameters is quite sad. I really thought this could have worked with the logic you explained. maybe the componentId changes when assigned to a parameters, I don't know. do you have documentation about the control boxes via javascript?
di...@gmail.com <di...@gmail.com> #11
Same observations here.. Both "view filters in report link" and formal "parameters" seem to be passed via the same exact "params" URL query parameter. However, for some reason only the filters use the global (report/page) scope when passed this way, while parameters operate at the data source level (only when passed over the URL). It also seems impossible to set the parameter from a page filter (another limitation of Data Studio..)
I should also note that pure filtering (without relying on formal "parameters") could actually do the job in a lot of cases, even more advanced ones [1][2]. But parameters may be unavoidable, for example, to pass the timezone to the data source query, and pure filtering won't work in such cases.
I've documented an example setup
[1]
[2]
mp...@connexion.tv <mp...@connexion.tv> #12
Thanks a lot. I'll have the devs to look into that, i mean the nginx implementation, that could help us regarding anohter of our needs. Appreciate your help.
[Deleted User] <[Deleted User]> #13
We are busy embedding datastudio into our website portal, as it is not possible to share an url parameter over multiple datasources we decided into the company to limit one datastudio dashboard to one dataset. In summary instead of a few datastudio dashboards with a menu to many pages we need now to create many dashboards linked together into our main portal. In the end this means a lot of overhead (developing time, testing, ....) .
Data studio is a great tool but it is missing these kind of small features which could turn it into an amazing tool beating PowerBi, Tableau, ... At least when it comes to bringing blazingly fast value to the customers with minimal design complexity and still having nice reporting features.
Anyway, Thx for providing datastudio,
Regards
te...@udhyam.org <te...@udhyam.org> #14
mp...@connexion.tv <mp...@connexion.tv> #15
mp...@connexion.tv <mp...@connexion.tv> #16
while other has over 400 and are still untouched from google.
while this one had 123 votes and was fixed (
It's really hard to tell whether or not they even acknowledged an issue or a feature request. Google is not really reactive to the post in this issue tracker. I would say, don't expect them to fix this and try to find a way around it or find another product. Otherwise, you might wait forever
ca...@seneca.io <ca...@seneca.io> #17
mp...@expertease.ca <mp...@expertease.ca> #18
Nope, all they do with the latest changelog we can see :
- change the name to looker studio
- make looker studio compatible with looker
- make looker studio comptabile with google analytics 4
- make right panels collapsable
- ignore the complaints regarding the modification they did
Have a look to the changelog yourself, basically all they do is update their connector to bigquery of Google Analytics
- 2022
https://support.google.com/looker-studio/answer/13139222 - 2023
https://support.google.com/looker-studio/answer/11521624?hl=en if loook in their community forum, you will see a lot of unresponded thread. People are pretty much on their own with looker studio
Best of luck
jo...@debortoli.com.au <jo...@debortoli.com.au> #19
I am currently developing a report with multiple BigQuery data sources. The report is linked through from an external system that dynamically updates some url parameters based on the page in the external system. I am trying to use parameters for filtering in BigQuery across all my data sources but it seems impossible from what I can tell by my research, but this is very important for my report.
Are there any workarounds that we know of for this in the meantime?
[Deleted User] <[Deleted User]> #20
[Deleted User] <[Deleted User]> #21
I have created dashboard in looker studio and there are 7 different widgets which need 7 store_id as parameter . Is there any way to pass single parameter from UI which should reflect all 7 widgets in dashboard. As of now.
var globalVar="store_id-123";
var params = { "1.store_uuid": globalVar, "2.store_uuid": globalVar, "3.store_uuid": globalVar, "4.store_uuid": globalVar, "5.store_uuid": globalVar, "6.store_uuid": globalVar, "7.store_uuid": globalVar };
I am passing above params json object which have repetitive values which doesn't look good
Sample dashboard URL:-
Could you please provide solution asap . I am stuck on this.
Description
When you have multiple data sources feeding a report, and all of these data sources use the same parameter e.g. a "customer id", there is no way to map a single URL parameter to each data source.
The URL parameter mapping page shows unique names for each data source:
ds0.CUST_ID
ds1.CUST_ID
etc.
and it does not allow changing the name to the same value.
This means that the URL must contain the same parameter value multiple times, which is ugly, creates longer URLs than necessary, and are difficult to create and manage. For example, if a new data source is added and uses the same value, all the report URLs must change as well, instead of the same report URL continuing to work without modification.
2) How do you plan on using this feature?
Abstracting data inputs into multiple sources is often necessary. This feature will allow for more effective report parameterization via URLs in this scenario.
3) What's the impact that this feature will have on you or your business? (Time saved, new users, etc.)
One week of developer time saved creating workarounds where we need to make report URLs dynamically generated instead of simply creating them once, plus ongoing maintenance costs.