I am new to visual force and I am trying to add a custom side bar to the service console.

I want to update this side bar here and I know you can't remove some of the fields that are on the standard object. enter image description here

So I have created a visual force page. Here is that code

<apex:page standardController="Case">
    <apex:pageBlock title="Case Details">
        <apex:pageBlockTable value="{!$ObjectType.Case.FieldSets.Case_Console_Fields}" var="f">
            <apex:column value="{!f}">
                <apex:facet name="header">Name</apex:facet>
            <apex:column value="{!f.Label}">
                <apex:facet name="header">Label</apex:facet>
            <apex:column value="{!f.Type}" >
                <apex:facet name="header">Data Type</apex:facet>

But when I preview the page I get this:

[![enter image description here][2]][2]

Which has no data and when I add it to the console layout I get this: enter image description here

  • Can you add 2nd image correctly? Jun 8, 2017 at 22:12
  • If I'm not mistaken, you can't add a page to the console, only a component instead. See the Service cloud Console developer' Guide for more. The 'undefined' that's displayed should be giving you a clue that things are inherited from the title bar, just like with a component.
    – crmprogdev
    Jun 9, 2017 at 6:21
  • Thanks Santanu, I will take a look at that. I thought I need the page for the component I will take a look at the guide.
    – Ericv
    Jun 9, 2017 at 15:26

1 Answer 1


Can you verify the 'Available for Salesforce mobile apps and Lightning Pages' flag (available when editing the VisualForce Page) is set ON? see here - https://www.screencast.com/t/uzFeeSDQVm

I have the same 'standardController' page which is showing just fine as a 'Custom Console Component'.

  • I tested your code in my sandbox, and was able to get the Customer Console Component alright (see here screencast.com/t/SDtFnwwdv). I suppose you might find an indicative error in the logs, to further troubleshoot this. Before doing so, verify that the VIsualForce Page has the appropriate Profiles associated (in the VisaulForce Pages list, hit 'security' next to your VF Page, and select the profiles to 'Enable Profile Access for Visualforce Page').
    – iDog
    Jun 15, 2017 at 6:59
  • iDog, I do have the profiles enabled correctly but I still am getting the error.
    – Ericv
    Jun 29, 2017 at 15:51
  • As I was able to receive the Custom Console Component in my SandBox with your code, I assume this should work. You'll have to further troubleshoot this with your 'debug logs' to reach the root cause.
    – iDog
    Jul 2, 2017 at 6:21

You must log in to answer this question.

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