ETL Change in behaviour

Jones01 · 2024-07-16T20:15:11+00:00

There was an error rendering this rich post.

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

Find more posts tagged with

Comments

rco

Thanks for your report. This change in behavior is not intended. You should see it working the way it used to within the hour.

timehat

The prior behavior has been restored.

timehat

@Jones01 on the note about date columns from Oracle landing into Domo as timestamps: what is the mechanism for ingest into Domo? Workbench, connector, custom API integration?

Jones01

@timehat

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.