Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
12 replies
Subscribers
5 subscribers
Views
4462 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
I am using getdatasubsetdownloadlinkfromrule and following the steps in document
kumaraveln
over 8 years ago
I am using getdatasubsetdownloadlinkfromrule and following the steps in documentation.
forum.appian.com/.../Download_DataSubset_Plugin.html
When I complete selecting the filter, URL is getting generated but when I click on the link, 500 - Internal Server Error is showing up. We tried several solution provided in other post but nothing worked. We were forced to move the report to a process model using a different plugin. Attaching the code snippet here. Appreciate any help.
Report_HomeScreen.txt
OriginalPostID-164135
OriginalPostID-164135
Discussion posts and replies are publicly visible
Parents
0
kumaraveln
over 8 years ago
Thanks chandhinir. Your suggestion worked.
And I made one more change. Since it was mentioned in the other post, the data subset has to be created by calling a rule one more time inside the rule (even if we have the datasubset obtained in parent rule) where we are constructing ExportableDataSubset object, I was passing three parameters (fromdate, todate and paginginfo) inside the rule. Now found that its not required. So I am just passing my pre-fetched data subset from parent rule as JSON and converting back into appian type and mapping it in ExportableDataSubset parameter.
So the modification i made on top of chandhinir's response is
Rule: Report_HomeScreen
getdatasubsetdownloadlinkfromrule(
rule!Report_getExportableDataSubset,
a!toJson(
{
datasubset_any: local!datasubset,
}
)
)
Rule: Report_getExportableDataSubset
with(
local!search: a!fromJson(
ri!input
), /*-- ri!input of type text) -- */
'type!{urn:appian:plugin:datasubsetdownload:types}ExportableDataSubset'
(
datasubset: local!search.datasubset_any,
fieldNames: {"requestStatus","requestId","ageOfStatus"},
fieldLabels: {"STATUS OF CDD","COUNT","AGING IN DAYS"},
filename: "AgingReport"
)
)
Please let me know if anyone face any issue in this approach
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
kumaraveln
over 8 years ago
Thanks chandhinir. Your suggestion worked.
And I made one more change. Since it was mentioned in the other post, the data subset has to be created by calling a rule one more time inside the rule (even if we have the datasubset obtained in parent rule) where we are constructing ExportableDataSubset object, I was passing three parameters (fromdate, todate and paginginfo) inside the rule. Now found that its not required. So I am just passing my pre-fetched data subset from parent rule as JSON and converting back into appian type and mapping it in ExportableDataSubset parameter.
So the modification i made on top of chandhinir's response is
Rule: Report_HomeScreen
getdatasubsetdownloadlinkfromrule(
rule!Report_getExportableDataSubset,
a!toJson(
{
datasubset_any: local!datasubset,
}
)
)
Rule: Report_getExportableDataSubset
with(
local!search: a!fromJson(
ri!input
), /*-- ri!input of type text) -- */
'type!{urn:appian:plugin:datasubsetdownload:types}ExportableDataSubset'
(
datasubset: local!search.datasubset_any,
fieldNames: {"requestStatus","requestId","ageOfStatus"},
fieldLabels: {"STATUS OF CDD","COUNT","AGING IN DAYS"},
filename: "AgingReport"
)
)
Please let me know if anyone face any issue in this approach
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data