Specify different date formats for multiple sources in ETL
I am combining a number of data sources with date columns using an ETL before performing other calculations on them.
Some of the sources have Australian date format (DD/MM/YYYY), and others have US format (MM/DD/YYYY).
The ETL gives me results in YYYY-MM-DD format, where it's actually incorrectly converted some of the dates to YYYY-DD-MM by assuming the wrong input date format. This means I end up with results from the future (eg 2018-12-03).
What's the best way to ensure the ETL always knows the correct input date format?
Comments
-
Hi. @artywah
Is it possible to avoid by replacing the date that is incorrectly converted by using regex?
Set Column Type
Column : DateColumn
Data Type: Text
Pattern A YYYY-MM-DD (TEXT)
Set Column Type
Column : DateColumn
Data Type: Date
Format : Year first
Pattern B YYYY-DD-MM (TEXT)
Replace Text
Column : DateColumn
Search "Use Regex": ^([0-9]*)-([0-9]*)-([0-9]*)
Replace : $1-$3-$2
Set Column Type
Column : DateColumn
Data Type: Date
Format : Year first0 -
Unfortnately this isn't working. It seems Domo is being too smart and processing the format before I can do anything with it in an ETL.
It seems I need to set the date format as Domo imports the data (before I can perform an ETL on it)
0
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