[SalesForce] Customized Related List in Visualforce, suppress edit/delete buttons

I am fairly new to Visualforce and I have been trying to create a Related List in VF on object Employee__c to show all of the devices with an ‘Active’ status (Status__c field on Device__c object).
There is a master-detail relationship on Device__c to Employee__c. The child relationship name is Relatedemployees.

I also tried to make sure the edit and delete buttons on the Related List do not appear.

Here are my codes:

Page:

<apex:page standardController="Employee__c" extensions="ActiveDevices">
     <apex:detail relatedList="true">
         <apex:relatedList id="CustomList" list="Relatedemployees" title="Active Devices" 
                           subject="{!actDevices}">
         </apex:relatedList>

         <style type="text/css">
                .actionColumn {display:none; visibility:hidden}
         </style>
     </apex:detail>
</apex:page>

Class:

   public class ActiveDevices {
       public List<Device__c> getactDevices() {
           List<Device__c> actDevices = 
              [SELECT Name__c, Type__c, Serial_Number__c, Status__c,  
                 FROM Device__c WHERE  Status__c == 'Active' ];
           return actDevices;
       }     
   }

Best Answer

This worked for me:

<style type="text/css">
            th.actionColumn {display:none !important; visibility:hidden !important} 
            td.actionColumn {display:none !important; visibility:hidden !important} 
</style>

Related Solutions

[SalesForce] The standard list controller and Custom Buttons on Related Lists

I completely agree. If you're not acting on a specific set of record in the related list with your custom button, i.e. if you're building a custom New button, there really isn't any need for a standard set controller. IMHO, salesforce should just have a standard way of passing over the details to a custom button and leave the visualforce page developer to figure out whether to implement with a custom controller, standard controller, or standard set controller depending on their specific requirements.

So why is it needed? I can only guess, but I would assume it's to prevent administrators from accidentally wiring up a button to a visualforce page that may not be able to accept your input.

That said, there are two ways to work around this. First, use a url for the source of your button. Using your example of a new task button on say an account record you could do

/apex/myCustomNewTaskPage?id={!Account.id}

Second, you can create the page and set the recordset var, create the button, then just edit your page. Once the button has been set up it doesn't enforce maintaining the recordsetvar attribute (although it may complain if you try and edit the button later).

[SalesForce] New, Edit, Save, Submit buttons in VisualForce page

I would recommend using FieldSets for your section layouts and perhaps add a toggle-able field widget:

<apex:component>
    <apex:attribute type="sObject" name="record" required="true"
        description="Record for which to display data" />
    <apex:attribute type="String" name="field" required="true"
        description="Field for which to display data" />
    <apex:attribute type="String" name="label" required="true"
        description="Label to display" />
    <apex:attribute type="Boolean" name="isEdit" default="false"
        description="Whether or not the field should be editable />

    <apex:outputLabel value="{!label}" />
    <apex:inputField rendered="{!isEdit}" value="{!record[field]} />
    <apex:outputField rendered="{!NOT(isEdit)}" value="{!record[field]} />
</apex:component>

Then in your View page:

<apex:pageBlockSection>
    <apex:repeat var="field"
        value="{!$ObjectType.Request_for_System_Change__c.FieldSets.LayoutSection1}">
        <apex:pageBlockSectionItem>
            <c:fieldWidget
                record="{!Request_for_System_Change__c}"
                field="{!field}" label="{!field.Label}" />
        </apex:pageBlockSectionItem>
    </apex:repeat>
</apex:pageBlockSection>

You would need to use a separate page for New and Edit and set the isEdit property to true.

Related Topic

[SalesForce] how to prevent the related list records from Edit and Delete function