Hi. Our Good Data environment is connected to a postgresql db and the timestamps in all the date columns are in UTC, e.g.

2024-11-13 20:41:12.254608

. When these are displayed in the visualizations, they are showing up as that time in the timezone that is selected without the proper offset applied, e.g. 8:41 PM instead of 2:41 PM (for US central time for example). How do I fix this? Thanks.

Hi Adam, if I understand the issue correctly, you would like to display the 24hr clock as represented in your data - You can do this by updating your “Date format” settings under the “Home” page and then going to “Settings” and from there you can see the option and timezone:

@Michael Ullock No. I want it to show in US central time in this case since that is what the timezone is set to in good data settings, i.e. show 2:41 PM ...not 8:41 PM like it is showing now

Thanks for the clarification 🙂 Please let our team review this and get back to you with more details on this asap

Yes. It doesn't seem too relevant since I set the timezone in settings to US central time already (see attached screenshot) and right now I don't need to set it on an org, workspace, or user level since I am just trying to get it to show properly at all. I see how it mentions "If your data is stored in the

DATE

or

TIMESTAMP

data types, no time conversion is available" but I have no idea how to see what data type you are storing it as. I just dragged in a date in the LDM and it doesn't say what type it auto picks (see screenshots for example).

Hi Adam, I have quickly tested this and it is working as expected for me, I made sure to declare the timestamps as "TIMESTAMPTZ" datatype. Please check the screenshot below for the results. You will notice how there is an offset of -8 hours (though my server displays the timestamps in my current timezone, CEST, hence the "+1" in the query results).

@Moises Morales Okay I confirmed that there are no workspace level timezone settings. I also found out that our postgres datatype for date+time columns are

timestamp

...so I casted them to

timezonetz

using your SQL dataset feature in the LDM like this for example:

select "completed_at"::timestamptz at time zone 'Etc/UTC' AS completed_at

However, when I do that, there is no longer an option in the visualization builder to pick Hour or Minute (see screenshot). Why would that be? I see times there when I run it in the SQL dataset UI (see screenshot). Also, when I change the timezone in the select to 'America/Chicago' or something then the times change when I click run, so I'm pretty sure my casting is working properly.

Thanks for trying that. In this case there seems to be a limitation as to what the CAST command can actually do, there are some known cases especially when working with PostgreSQL, in other words, the CAST will not work as intended for the timestamp datatype conversion. Are you having any troubles declaring your timestamp as "timezonetz"? You could try it from a view to test quickly.

Oh I figured out why hour and minute weren't showing, these weren't checked by default when I dragged in the new date into the LDM. Looks like there might be an AM/PM issue now though. Stand by.

I am glad to hear it is now working! I am not sure if I follow, I do agree that setting the timezone via the URL paramenter of an embedded dashboard would be handy in any case, nonetheless setting the timezone for individual users or workspaces within an organization is possible via the API: https://www.gooddata.com/docs/cloud/customize-appearance/manage-timezones/#ManageTimeZones-Users

Yes I saw how to set time zone via the API at the workspace or user level and I am currently using it at the workspace level, which gets us at least some of the way there. The issue is that with our 100% embedded implementation, we only have one good data user per workspace (i.e. workspace = one of our enterprise customers with many users). In other words, we cannot have one good data user per user on our platform for technical reasons that would take too long to explain in a message. Thus, the feature request is to be able to set the time zone at the time of the embed. This would be the only way to allow our users who are in a workspace/enterprise see the proper time zone if they do not happen to be in the time zone I set for the workspace...which is often the case since many of our customers have employees around the country/world. Please go ahead and submit the feature request. Thanks Moises.

🎉 New note created.

Thanks for the details! I have shared this internally with our developers so it gets considered for future Product releases. Please note that I cannot promise it will ever be implemented, but depending on how critical this is for you, I strongly recommend discussing it with your Account Manager @Pavel Doubek as well

Understood. Thanks