Following up on this. I was talking internally and we do have timezone settings set, and i can see tey are working, but they are not coming up in the org settings

Hi Doug, I’ve been testing on my end. I posted a new timezone via POST to

{{baseUrl}}/api/v1/entities/organizationSettings

, and afterward a GET to the same endpoint did list the new entry. Can you tell me a bit more about the endpoints and methods you used for your calls?

They say that it is in the right format. It works for all other workspaces, but this specific one - its not working. We tried updating it to different timezones to rule out the naming

Just to conclude this one: We discussed and investigated this a bit further and found that the issue was indeed related to the fact that the Data Source did not have the

TIMESTAMPTZ

data type, which is necessary for the Timezone feature to work correctly. Once that is added to the data, everything will work as expected 🙂

@Francisco Antunes Ok so the solution is to change to TIMESTAMPTZ. However, in databricks this is not a data type. What have other customers done?

I’m currently not aware of other implementations of Databricks that encountered this, but checking their documentation I noticed that the TIMESTAMP data type does allow for a

zoneId

, where you can append

+hhmm

(e.g.,

+0000

) to specify the timezone of the timestamp. Is the data already arranged this way? I’m checking internally whether that would allow for GD Cloud to identify these columns’ data types as

TIMESTAMPTZ

.

Yes, we were thinking of appending the zoneid, to our timestamps. second question: would it be an issue if we just added it to some timestamps and not all? Or do we need to add it to all?

You don’t have to add the time zone to all Date dimensions, necessarily; But, those dimensions (tables) to which you do add them, it must be to all the datapoints.

@Francisco Antunes did you ever finish checking internally "I’m checking internally whether that would allow for GD Cloud to identify these columns’ data types as

TIMESTAMPTZ

."

Hi Doug, I’ll go ahead and reply on the new thread, to keep things better organized on our end, OK?