Transform Timezone for Entire Dataset
I've been incorrectly bringing data into a dataset (appending) for months now assuming it was coming in as UTC and then Domo converting it to EST. However apparently the data was in EST the whole time and being incorrectly represented in Domo since it was being converted. I know I can add the transform to the Workbench job to correct the data going forward however I have all this past data that I need to convert. What's the best practices here?
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**
Comments
-
Does the database that your workbench is pulling the data from still contain your historical data?
If so, you could run the job once as a full replace and then switch it back to an append
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman0 -
Unfortuantely it does not, if contains X most recent records that get replaced as more come in so I have a lot of stuff that doesn't exist anymore
**Make sure to like any users posts that helped you and accept the ones who solved your issue.**0 -
I would recommend running the historical data through a dataflow and utilizing the convert timezone function to convert the field to UTC.
-----------------
Chris0
Categories
- All Categories
- 1.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 282 Workbench
- 3 Cloud Amplifier
- 4 Federated
- 2.8K Transform
- 86 SQL DataFlows
- 548 Datasets
- 2.2K Magic ETL
- 3.2K Visualize
- 2.3K Charting
- 544 Beast Mode
- App Studio
- 26 Variables
- 566 Automate
- 134 Apps
- 411 APIs & Domo Developer
- 21 Workflows
- DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 345 Distribute
- 87 Domo Everywhere
- 257 Scheduled Reports
- 1 Software Integrations
- 85 Manage
- 84 Governance & Security
- 8 Product Release Questions
- Community Forums
- 41 Getting Started
- 27 Community Member Introductions
- 81 Community Announcements
- 4.8K Archive