Export DataStoreEntity to Excel - Timezone Issue

Question

Hi Team, 
 I have requirement to run on scheduler to create case based on configuration and export some transactional data in the excel file, send an email. In the excel there is one column with datetime type is one of the columns and in the excel always it is exporting as the usertimezone. Example : This scheduler PM always run around 01:00 AM CST and last published designer time zone is GMT.As this user is administrator across platform level, so don't want to change user time zone to CST. Please find below items for reference. 
 
 1. I have run the PM in the CST timezone,Stil in the exported excel file taking the last published Administrator account time zone (GMT). 
 2. I can do it in data base, but i don't see any dynamic function to convert automatically handle daylight savings (Without hardcoding +06:00 hours..etc). 
 
 Can you please help me out to export excel the column data datetime as CST timzone. 
 
 Thanks and Regards 
 Venkatesh Suram

Mike Schmitt · Answer

One of my long-held feature requests for the Export DSE to Excel node, beyond the absolutely critical missing capability to use a preformatted template file (this one makes it basically unusable for me on any routine basis), is the ability to do Appian-side transforms on the data. Such as returning just the date from a dateTime (or other date transformations), or the Friendly Name (per the Appian Account) for a stored username. 
 Stefan beat me to the reply but the other thing I was going to mention, if push comes to shove you could probably transform the rendered DateTime within a View, then use the View as the source for your Export to Excel.

Mike Schmitt · Answer

What evidence do you have that the export is observing the user's time zone (or any other time zone) at all ? It sounds to me like it's just exporting the value found in the DB which will always be GMT/UTC.

Mike Schmitt · Answer

Thanks for clarifying. I'm not sure whether there are any easy workarounds then, if you're not able to change the user time zone for the Administrator/Publisher account to your local time zone (then again, there might not be any good reasons NOT to do that, or at least try it in your Dev environment and see if it works).