Magic ETL
Magic ETL
ETL Change in behaviour
Hi,
Just to help any one that runs into the same problem. I noticed tonight that TIMESTAMP columns with times set to 12:00:00am no longer join to DATE columns.
This changed some time today.
I have had to adjust the column within the ETL in the data handling section of the input.
Luckily there was only a handful of sources to update.
There doesn't seem to be a way to get a DATE column from ORACLE over to DOMO without it changing it to a timestamp. If anyone knows a way I would love to know.
Thanks
Comments
-
Thanks for your report. This change in behavior is not intended. You should see it working the way it used to within the hour.
Randall Oveson <randall.oveson@domo.com>
0 -
The prior behavior has been restored.
0 -
Thanks both.
We use the Oracle SSH connector. In Oracle dates do have a time component so I don't think this can actually be removed hence why they end up as timestamps in domo.
We have scenarios where we would like to keep the time element so a timestamp is fine but when the time element to the date is 00:00:00 casting to a domo DATE would be nice as an option.
0
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 7 Cloud Amplifier
- 9 Federated
- 3K Transform
- 114 SQL DataFlows
- 654 Datasets
- 2.2K Magic ETL
- 4.1K Visualize
- 2.5K Charting
- 802 Beast Mode
- 79 App Studio
- 44 Variables
- 758 Automate
- 188 Apps
- 480 APIs & Domo Developer
- 73 Workflows
- 17 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 408 Distribute
- 119 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 141 Manage
- 137 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive