How to import date/time values in workbench exactly as 8/26/2024 9:00:49 AM, without any transform?

I am using the Domo workbench to import data that includes two fields, OrderDate
and TransactionDate
, which are in date/time format. My goal is to import these date/time values exactly as they are, without any modifications or timezone shifts. For example, if the OrderDate
is 8/26/2024 9:00:49 AM
, I want it to be imported into Domo as 8/26/2024 9:00:49 AM
, without any changes. My date/time values are successfully being created in the tool, showing as a date/time value…but 5 hours are being subtracted.
I am aware that there is a "Shift Data Timezone Transform" option in the Workbench, but I do not want to use this transform as it alters the original date/time values. I need to ensure that the date/time stamps are imported exactly as they are in the source data.
Is there a specific setting or configuration in the Domo Workbench that I might be overlooking which would allow me to achieve this? I need guidance on how to import the date/time fields without any transformations or shifts?
Answers
-
In your schema you can define it as a STRING instead of a DATETIME so it'll import the characters exactly as defined.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**2 -
Thank you Grant, I am trying your suggestion now.
0 -
Excellent Grant, I defined it as a STRING instead of a DATETIME and the values are now coming in identically, but those two date fields are now coming into Domo as text fields. Unfortunately, in my cards, I need those two date fields to be functional (calendar format). Is there a solve that I could implement that doesn't include a workflow, even downstream before the data is used in cards, that would allow me to use them as calendar format?
0 -
When a date is imported into Domo it's assumed that it's UTC. If you want to treat it as a date then you'll need to import it as a date. If the date doesn't align with what you're expecting due to the time zones then you'll need to use a Timezone transform and import it with the timezone your source system is set with. This will allow it to be imported with the correct time in relation to UTC. Once you have the data and it's displayed on a card the Company Settings will take effect and translate your timestamp stored in UTC as whatever your timezone is set to.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 305 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 107 SQL DataFlows
- 648 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 775 Beast Mode
- 75 App Studio
- 43 Variables
- 734 Automate
- 186 Apps
- 471 APIs & Domo Developer
- 63 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 403 Distribute
- 117 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 137 Manage
- 134 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive