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
10 replies
Subscribers
5 subscribers
Views
3250 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Plug-Ins
downloaddatasubset plugin error
Alok Patro
over 7 years ago
Hi All,
I am using this downloaddatasubset plugin. It was working fine.
But today am getting an internal server error.
Any inputs.
OriginalPostID-235926
Discussion posts and replies are publicly visible
0
narasimhaadityac
A Score Level 2
over 7 years ago
Hi alok, could you please check the application server log? It should give you more info on this error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mognons
A Score Level 2
over 7 years ago
Double check the dictionary you built up to list field columns and values and, most important, rememember that the parameter name, if used, MUST be "input" of type String: nothing else, or you'll get the above error...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alok Patro
over 7 years ago
@narasimhaadityac - Application server log is not enabled in my could instance. any other suggestions
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mognons
A Score Level 2
over 7 years ago
@alokp190 Did you check my suggestions? I did lose a whole afternoon struggling with the same error, only to discover that I chose to name the function parameter to my likings, which is quite a bad idea.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mognons
A Score Level 2
over 7 years ago
On the same line: check that the resulting dataset is returned before the plugin times out... The timeout value is clearly stated in the plugin documentation
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alok Patro
over 7 years ago
@albertom32 : yes variable name is input and is of type text
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alok Patro
over 7 years ago
Even the data is being captured properly
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 7 years ago
@alokp May I please know why the 'data' in 'ExportableDataSubset' is in the object format? As far as I remember, it looks similar to contents of 'data' attribute in any other normal or plain DataSubset. I would suggest keeping an eye on it and as per my experience it happens at times when the DataSubset is unable to understand the 'data' and finally stores in an object format after failing in recognising/understanding the format of the data.
Also, would you be able to let us know how you are building the 'datasubset' attribute in the ExportableDataSubset?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alok Patro
over 7 years ago
I checked a few other implementations for this plugin and it is the showing the same error. It is some issue with the cloud instance ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
sikhivahans
over 7 years ago
@alokp Well, I couldn't really say about it until we have got some clue from logs. Raise a support ticket or ask those who has the access to do so and inspect the logs to check the presence of the error related to the plugin.
Prior to doing as mentioned above, I would suggest making sure that the rule being used to return the DataSubset is correct and I doubt that this is the place where it's failing. Would you be able to execute the type!ExportabeDataSubset definition in an expression rule (along with fields and rule used for data) and see what it's returning? Also it would be good if you can describe about the rule that populates the 'data' attribute in ExportableDataSubset.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel