Skip to content
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.

Please add the user_timezone property to the embed examples #18

Open
les2 opened this issue Mar 24, 2017 · 1 comment
Open

Please add the user_timezone property to the embed examples #18

les2 opened this issue Mar 24, 2017 · 1 comment

Comments

@les2
Copy link

les2 commented Mar 24, 2017

It is claimed that user_timezone can be specified here: https://discourse.looker.com/t/user-specific-time-zones-3-22/875/8 and https://discourse.looker.com/t/looker-3-34-release-notes/1682

vincentFeb 1
Hi @Jay_Stricks,

To set an embed users timezone, in the same query params that you put the permissions, models, etc, you add another one like so user_timezone: json_user_timezone. Let me know if you have any questions on this.

Cheers,
Vincent

and

Powered By Looker
PDF Downloading for Embedded Dashboards. Permissions are configured in the same way as for regular Looker Users and Roles.
All Download Types for Embedded Elements. Permissions are configured in the same way as for regular Looker Users and Roles.
User Timezones for SSO Embedding. Set the parameter as part of the SSO embed setup process.

But there is no complete example of this and the feature is not documented in the PDF embedding instructions provided by Looker (update: i do see the parameter listed in the PDF document). This makes the API really, really difficult to use. Does the user_timezone parameter need to be included in the request signing? Is it just a dashboard filter parameter?

Furthermore, the python example here: https://github.com/looker/looker_embed_sso_examples/blob/master/python_example.py does not use the user_timezone parameter.

@jbandhauer
Copy link
Contributor

I agree. Looks like it got added only to the ruby example:
https://github.com/looker/looker_embed_sso_examples/blob/master/ruby_example.rb#L76

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants