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
2 replies
Subscribers
7 subscribers
Views
1066 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
RE: Extra (blank) CDT record created when a Portal form is generated/opened in p
ryanh
over 9 years ago
RE: Extra (blank) CDT record created when a Portal form is generated/opened in production
System: Appian 7.4 Hotfix E, Windows 2008 server, MS SQL, Portal interface
During a deployment validation of a few updates (unrelated to error) a user was entering a test order into our production system. As the process continued through the Portal interface a few script tasks ran and then a Portal Form node was run. The user experienced a system Alert when they submitted the form and the process model stopped with an alert. Upon investigating I found what appeared to be a CDT with 2 records in it, the 2nd one blank (but still showing each individual CDT variable with blank values). The form uses this CDT in a Grid element and the user is permitted to select 1 row from the grid to perform an action on, or selecting items from a drop down on each row.
On the parent model as well as nodes BEFORE this form the CDT had the correct number of records (1) with valid data...
OriginalPostID-124557
OriginalPostID-124557
Discussion posts and replies are publicly visible
0
ryanh
over 9 years ago
... in it. According to the history it appears as if a 2nd blank row was added to the grid. The alert happened because once the form was submitted a later script task performed a query rule on the data and used the CDT values as inputs, the 2nd blank row had a blank/null value which couldn't be passed into the query rule successfully.
I've seen this type of issue occasionally before where the form appears to show either a 2nd row in the grid or the CDT itself has a 2nd value. This error hasn't happened lately and appears to have happened when the form was opened versus a script task manually appending a blank record.
I was able to fix the problem short term by adding a script task with a data output assignging the 1 good record to the whole CDT thereby deleting the blank one (setting pv!theCollateral = pv!theCollateral[1]). This fixed the issue and let the user continue. However, we haven't been able to reproduce the problem and generate a blank row again.
Has ...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
ryanh
over 9 years ago
...anyone seen similar issues? Does the grid occasionally add a 2nd row (I've seen it when the values in the grid have an errant semicolon/delimiter that tricks the system into thinking there are n+1 records).
Thanks, Ryan
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel