Hi, Am using export to excel plugin - getdatasubsetdownloadlinkfromru

It looks like the time that is exported to the report is converted to GMT. Depending on your report configuration you can probably work around this by using the local() function.

Another alternative could be the Download DataSubset plugin: forum.appian.com/.../Download_DataSubset_Plugin.html

Yes, am using ExportableDataSubset plugin and below is the code i have modified using local(), its giving 500 internal server error:
c2:apply(rule!BWIS_WF_REP_convertToLocal,local!datasubsetNew.data.c2)
convertToLocal code - if(or(isnull(ri!dateInput),ri!dateInput=""),ri!dateInput
local(ri!dateInput,"PDT"))

@ryan: Please tell us if this understanding is correct.

1. Say my date time value for a record is 5Nov2015 10:30 AM in database (which is GMT)
2. When I query the entity and form the data subset, date and time will come unchanged
3. When apian renders the value in grid, it converts it to user preferred time zone, which in our case is PDT.
So user will see something like 5Nov2015 02:30 AM PDT (- 8 hrs)
4. Now when I try to export to excel, the plugin takes the source data from my datasubset because of which it is displaying the date time value present in DB instead of the one in UI.
5. But for user it looks odd to see the conflict between UI and excel although time zone is specified in UI. (We noticed that wherever a time is in GMT, zone not explicitly mention. Both in table and excel. May be this something usual. But end user may be confused on this)


Now we are not clear with #2 and #3.
Whether the date time value will be converted to preferred time zone at the point of querying (when obtaining datasubset) or rendering in grid.

If datasubset itself is having date and time in PDT, then should we check if the plugin is trying to convert it back to GMT at some point.

its +8 hours

For a detailed description of how dates/times are converted, check out the docs here: forum.appian.com/.../Time_Zone_Context.html

Thanks ryan. That helped a little in understanding. But sure how to resolve the issue now.

PFA .. Found a small spell err in the documentation .. if you are interested :)

*But not sure how to resolve the issue now.

I think you can get around this behavior by using the local() function

forum.appian.com/.../Date_and_Time_Functions.html

You would need to change the report column definition to local( XXX ) where XXX is the current value. Then you should see the datetime exported in the local timezone.