My testing has shown that when a datetime field is input from a Snowflake table, the Input tool will convert the data to reflect the datetime as local time to the machine the workflow is run on.
For example, this is a data set from a direct query to Snowflake...
![RodLight_0-1650405192656.png RodLight_0-1650405192656.png](https://community.alteryx.com/t5/image/serverpage/image-id/231796iFA403A019A136FC5/image-size/medium?v=v2&px=400)
This is what is coming out of the Input tool with the machine set to Pacific time...
![RodLight_1-1650405305908.png RodLight_1-1650405305908.png](https://community.alteryx.com/t5/image/serverpage/image-id/231799iB7425FE4A902D18D/image-size/medium?v=v2&px=400)
However when setting the machine to Central time, the results from the Input tool are...
![RodLight_2-1650405405523.png RodLight_2-1650405405523.png](https://community.alteryx.com/t5/image/serverpage/image-id/231800i5C1D3F9CE4272C18/image-size/medium?v=v2&px=400)
This obviously can wreck havoc with inconsistencies of subsequent reporting off of this data.
Since Snowflake carries the UTC offset as part of the data, it would be nice to have the ability to disable this "assumption" by Alteryx that the results should convert the datetime to the machine datetime. This way the data could pass through with the datetime values that are held in the database.