I have added a multi-record list button to the Contact object that forwards the selected records to a custom VisualForce page that is defined below.

<apex:page standardController="Contact" recordSetVar="selectedContacts">
    <apex:form >
        <apex:pageBlock id="pb" title="Selected Contacts">
            <apex:pageBlockTable id="pbTable" value="{!selected}" var="c">                    
                <apex:column value="{!c.id}"/>

This button works as expected in most cases. However, when a Topic filter (screenshot below) is used on the Contact list view I get the following exception when clicking on the button:

system.security.NoAccessException: Object type not accessible. 
Please check permissions and make sure the object is not in development mode: 
Contact WHERE ( ((Topics INCLUDES 'Demo')) AND (id IN ('003F000001LLMhJIAX' 
^ ERROR at Row:1:Column:88 expecting a left parentheses, found 'Demo' 

Screenshot of the Topic filter

Screenshot of the Topic filter

Question: What could be causing this problem?

  • Using INCLUDES in queries typically requires an array of comma delimited values and I would have expected to see it written as Contact WHERE ( ((Topics INCLUDES ('Demo') )) AND even though there is just a single value in the list. This is also consistent with the error message. Is this a query which you created in code or is it auto-generated by the List View's filter criteria? Can you add a picture of the Filter Criteria on your view?
    – Mark Pond
    Commented Apr 29, 2014 at 0:55
  • Hmmm, this looks like a bug in the StandardSetController to me. Commented Apr 29, 2014 at 10:34
  • Just been looking to see if I can reproduce this, can you include a screenshot of your List View definition please? Commented Apr 29, 2014 at 10:43
  • @Pond The filter is from a standard list view. I have added a screenshot of the filter to the question.
    – cseaton
    Commented Apr 29, 2014 at 14:14
  • I've also opened a case with Salesforce. No response yet.
    – cseaton
    Commented May 1, 2014 at 14:58

1 Answer 1


This behavior has been identified as a bug by Salesforce.

Track the status of this issue here.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .