I'm using the Download DataSubset (on-premise) plugin in order to export dat

lesliem over 9 years ago

I'm using the Download DataSubset (on-premise) plugin in order to export data to excel. I am using the JSON strings to pass multiple input parameters to the export rule. I am passing 2 DateTime paramters and a Text parameter. My input parameter is a type Text and I use the todatetime function to convert the 2 DateTime parameters from string to date within the export rule. If I use a range of 03/12/2015 12:00 pm - 03/19/2015 12:00pm in the report I get 41 records dates from 03/12/2015 12:30 pm - 03/19/2015 6:40am. But when I export them to excel using the rule I get 37 records. The datetime from the CDT are in GMT time but the input start and end dates are local Has anyone else used this plugin and had this issue? How do I convert the datetime to local time on the export?

Here is the call to the export rule:
local!ruleURI3: getdatasubsetdownloadlinkfromrule(rule: rule!ruleURI3, input: a!toJson({receivedDateTimeStart: tostring(local!receivedDateTimeS...

Discussion posts and replies are publicly visible

0 lesliem over 9 years ago

...tart), receivedDateTimeEnd: tostring(local!receivedDateTimeEnd), filter: local!PMNameFilter})),

Here is the export rule:
=with(
local!search: a!fromJson(ri!input),
'type!{urn:appian:plugin:datasubsetdownload:types}ExportableDataSubset'(
filename: "CA Event by Est. Proc. Date BLANK_"&now(),
fieldNames: {
"caEventId",
"securityId",
"ticker",
"electionTypeDescription",
"actionTypeDescription",
"subActionTypeDescription",
"estimatedProcessingDate",
"receivedDate",
"expirationDate",
"exDate",
"effectiveDate",
"currentStatus"
},
fieldLabels: {
"Event ID",
"Security ID",
"Ticker",
"Election Type",
"Action Type",
"Sub Action Type",
"Est. Processing",
"Rec'd Date & Time",
"Expiration",
"Ex Date",
"Effective",
"Current Status"
},
datasub...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lesliem over 9 years ago

...set: if(isnull(local!search.filter),rule!SO_CA_GetCAEventDetailsWithPMIsProcessingCompleteFalseBlankEstProcDate(fn!todatetime(local!search.receivedDateTimeStart), fn!todatetime(local!search.receivedDateTimeEnd),a!pagingInfo(startIndex: 1, batchSize: -1)),todatasubset(index(rule!SO_CA_GetCAEventDetailsWithPMIsProcessingCompleteFalseBlankEstProcDate(fn!todatetime(local!search.receivedDateTimeStart), fn!todatetime(local!search.receivedDateTimeEnd)), where(search(local!search.filter, rule!SO_CA_GetCAEventDetailsWithPMIsProcessingCompleteFalseBlankEstProcDate(fn!todatetime(local!search.receivedDateTimeStart), fn!todatetime(local!search.receivedDateTimeEnd)).manager)), {}),a!pagingInfo(startIndex: 1, batchSize: -1)))
)
)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Aleksi White
Appian Employee
over 9 years ago

You can use the local() function to convert datetimes to your timezone:
forum.appian.com/.../Date_and_Time_Functions.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lesliem over 9 years ago

With this plugin I don't know how I would do that, unless I change the plugin.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Aleksi White
Appian Employee
over 9 years ago

Ah, I was thinking you could do the conversion before sending the data through the plugin. If you try that does it give you any different results?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lesliem over 9 years ago

If I convert my start and end datetime parameters to GMT before sending them to the plugin my results will be different than the results of the report which are using MDT. I will be getting records for received dates 6 hours ahead of MDT.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shivakanthr over 7 years ago

Is this issue resolved as i have same requirement?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel