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
Discussion posts and replies are publicly visible
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.
If i understand correctly mike. As i mentioned in the #1 in description, do we have any dynamic function to handle daylight saving as well in the Maria Database to handle in the DB View.
If you create a new view for this purpose, my assumption is that you can simply add the appropriate number of hours to the column's value (within the view, using standard SQL functionality), such that the data returned by the Excel from DSE node will appear correct. It would be worth a try, at least.