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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 738 Beast Mode
- 56 App Studio
- 40 Variables
- 684 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 123 Manage
- 120 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive