How is Timezone inherited from source then converted?
I have a dataset coming in from the Gong connector and some timestamps come in as text fields (scheduled, started). Our Domo timezone is set to Eastern. When I cast data type as timestamp, the times move up 3 hours.
Should I assume the Gong source data is Pacific (Gong is in SF) and Domo is inheriting the timezone properly? I don't see anything in the connector that indicates it is PT and I had thought Domo assumed times were UTC.
Best Answer
-
I think I've figured it out. All good now!
0
Answers
-
I think I've figured it out. All good now!
0 -
When ingesting data Domo assumes UTC and when it gets to a visualization (in a card or on the dataset data tab) Domo will then convert your data to the Timezone company setting. Are there any other transformations happening on your data during processing or just converting it to a timestamp?
Have you tried using the STR_TO_DATE function in a formula tile and specifying your own format string to convert it to a date and are you still getting the timezone offset issue?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 605 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 696 Beast Mode
- 43 App Studio
- 39 Variables
- 660 Automate
- 170 Apps
- 442 APIs & Domo Developer
- 42 Workflows
- 6 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 388 Distribute
- 111 Domo Everywhere
- 271 Scheduled Reports
- 6 Software Integrations
- 113 Manage
- 110 Governance & Security
- 9 Domo University
- 31 Product Releases
- Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive