tag:blogger.com,1999:blog-703101161281072462.post2930724178181380675..comments2024-02-28T06:01:47.440-08:00Comments on Development Memoirs: selectCheckboxes and commandbuttons in Sales ForceJeremyhttp://www.blogger.com/profile/11674418943047372077noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-703101161281072462.post-86679864169171532992011-10-15T17:16:21.663-07:002011-10-15T17:16:21.663-07:00That is great information, thank-you for sharing. ...That is great information, thank-you for sharing. I will have to try that out the next time I am working in SalesForce.Jeremyhttps://www.blogger.com/profile/11674418943047372077noreply@blogger.comtag:blogger.com,1999:blog-703101161281072462.post-22178188954884163502011-10-14T09:28:41.699-07:002011-10-14T09:28:41.699-07:00I ran into this problem and found your post. Here...I ran into this problem and found your post. Here's what I found:<br /><br />1) apex:selectCheckboxes returns a *list* of strings, which no database field (like multi-select) will accept in its raw form. If this component is assigning a value to an object field, it will throw an error.<br /><br />2) By using the apex:selectCheckboxes component, the on-screen error you usually get with apex:inputField is not included. So you have to add an apex:message component to reveal and confirm the problem.<br /><br />The solution is to use a custom variable in the controller that accepts List and then (if needed) translate that value to an appropriate format during the submit.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-703101161281072462.post-33019371158796314662010-01-03T23:17:11.112-08:002010-01-03T23:17:11.112-08:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.com