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
19 replies
Subscribers
8 subscribers
Views
8121 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
How do I save multiple selections in a checkboxField? I tried displaying the cho
judym598
Certified Senior Developer
over 9 years ago
How do I save multiple selections in a checkboxField? I tried displaying the choiceValues using a rule (e.g., rule!psh_getAllFruits) that pulled data from a cdt (PSH_Fruits). The CDT is associated with a table (pshfruits) that has 2 columns: id (auto-generated integer) and fruitType (text). I wanted to store the selected id(s) in a field in another CDT (specifically newList_cdt.fruitType). I originally had 'fruit' as an integer. When that didn't work, I decided to change my approach to displaying the choiceValues using a constant (cons!PSH_FRUITS) and using a checkboxFieldByIndex; couldn't get that to work, so I went with the following and changed the data type of the column in the table (and CDT for this item) to 'text'. It works as long as I only select one item. (I actually have 8 choices so I'd really prefer to pull the choiceValues from a CDT - lookup table). I cannot get it to save or display multiple selections. At one point...
OriginalPostID-192632
OriginalPostID-192632
Discussion posts and replies are publicly visible
Parents
0
jackm829
A Score Level 3
over 9 years ago
1. My approach doesn't necessarily entail a new table, or a nested CDT. It could be the same table as is.
2. If using the 'split' method, make sure to consider the effect of "name changes" - what happens if "Bananas" go by "BN" instead of "B" in the future? What are the application effects? If necessary to account for this, a lookup table could be used & this is compatible with other approach.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
jackm829
A Score Level 3
over 9 years ago
1. My approach doesn't necessarily entail a new table, or a nested CDT. It could be the same table as is.
2. If using the 'split' method, make sure to consider the effect of "name changes" - what happens if "Bananas" go by "BN" instead of "B" in the future? What are the application effects? If necessary to account for this, a lookup table could be used & this is compatible with other approach.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data