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
4 replies
Subscribers
7 subscribers
Views
1042 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Grid Links Malfunctioning after 17.1 upgrade
andrewo987
over 7 years ago
While smoke testing our environment directly following an upgrade to 17.1, I ran into strange behavior with editable grids and their "addRowLinks". One of our forms contains multiple editable grids. When accessing this form from sites, all of the "addRowLinks" fail to add a row in their respective grids. It almost looks like the page never is submitted to Appian. None of the text fields will update the page. Pressing any submit buttons won't trigger validation either.
When accessing the exact same form/task from tempo, the link issue changes. Many "addRowLinks" begin to work as designed, but some will throw an error (attached is the Chrome error). The buttons are still unresponsive in tempo.
All the above interfaces did not malfunction before the upgrade. It seems to be localized to this form, as the rest of the system appears to be functioning properly. Has anyone r...
OriginalPostID-268430
Discussion posts and replies are publicly visible
0
andrewo987
over 7 years ago
...un into these issues before?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mike Schmitt
Certified Lead Developer
over 7 years ago
Can you perhaps try running a debug process with a simplified version of the functionality found on the form that's malfunctioning? It might be best to try to narrow down exactly what the issue is, and ruling out anything unique the current form does, etc.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
andrewo987
over 7 years ago
Thanks Mike! I ended up opening a support case and they suggested the same thing. If Appian support is unable to come up with a resolution we might have to allocate the time to make one. This could take some time to investigate since the error does not manifest in the interface designer and the form is quite large. I will add to this thread if we are able to find a solution.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
andrewo987
over 7 years ago
Root cause ended up being a blank "a!radioButtonField()". It caused the interface break when viewed in both tempo and sites. The workaround was to remove this line. Appian cloud acknowledged it was unintentional behavior and was working on a fix.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel