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
7 replies
Subscribers
7 subscribers
Views
8535 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
The contents field on a column layout may only contain components. Received Save Tree at index 12.
martinc8721
over 7 years ago
I've go the following pinkbox message when trying to access to a related action
Expression evaluation error in rule '*InsertRuleNameHere*' at function a!formLayout [line 98]: The contents field on a column layout may only contain components. Received Save Tree at index 12.
Any idea why is this happening?
Thanks.
OriginalPostID-270078
Discussion posts and replies are publicly visible
0
Josh
Certified Lead Developer
over 7 years ago
Does the form error out when you open it up in interface designer?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
martinc8721
over 7 years ago
no it does not, the interface works if I access to it using a task, I guess is a ri! that is missing
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Josh
Certified Lead Developer
over 7 years ago
I would troubleshoot it in the interface designer, get it to work there, and then move on to the related action to see how it is invoked and if there are any mismatches.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
martinc8721
over 7 years ago
I have found the issue, it was one of many embedded interfaces which was returning
{
save(ri!testing,true,true)
},
the code breaks because appian is expecting a interface component but is getting the save tree.
Thanks for your help Joshl
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
I believe this error is referring to an a!save() you may be doing within your form in an inappropriate place or just doing the save inappropriately but I could easily be wrong.. Take @joshl's advice and just go over the components of your interface.
it's somewhat difficult for me to pinpoint without seeing the code itself.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
reginaldm377
over 7 years ago
@martinc872 ignore my previous comment. I see you found the issue a moment ago.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
martinc8721
over 7 years ago
thanks @reginaldm377 for your contribution
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel