Visualforce page not listed when overriding Tab.

  • 1
  • Question
  • Updated 3 years ago
  • Answered
I'm following this tutorial
And I created a VF Page 'RamoTab' with the code:

<apex:page standardController="alas1__Ramo__c" recordSetVar="c" extensions="skuid.Redirects" action="{!redirect}?page=RamoTab">

But when trying to override the default Tab (Step 8 of the link) my page is not listed. If I try to override the List instead of the Tab I do get the page listed. What am I missing?

Consider that: I'm on an org with namespace 'labs01' which has Skuid installed and my 'alas1' managed package as well. The VF page 'RamoTab' is under 'labs01' namespace.

Photo of Sebastian Canseco

Sebastian Canseco

  • 358 Points 250 badge 2x thumb

Posted 5 years ago

  • 1
Photo of Emily Davis

Emily Davis, Employee

  • 3,578 Points 3k badge 2x thumb
Hi, Sebastian,
Are you trying to override the tab for the alas1__Ramo__c object? The object whose tab you are overriding has to match the standardController object in your Visualforce code.
Photo of Sebastian Canseco

Sebastian Canseco

  • 358 Points 250 badge 2x thumb
You're correct. That is what I'm trying to do. The object name is alas1__Ramo__c as in the VF code.
Photo of Zach McElrath

Zach McElrath, Employee

  • 52,276 Points 50k badge 2x thumb
The issue here has to do with the Managed Packages. Here's the deal:

From your org that has the "labs01" namespace, to override the Tab action for an object included in the "alas1" Managed Package, you have to NOT specify a Standard Controller. Rather, change the redirect override syntax to be:

<apex:page controller="skuid.Redirects" action="{!redirect}?page=RamoTab"/>

Moreover, you will not be able to override actions of any other type for objects in the "alas1" managed package, from the "labs01" org.  This is a very annoying restriction that Salesforce has in place for overrides, preventing you from overriding actions of objects that come in managed packages.
Photo of ddeveaux


  • 1,212 Points 1k badge 2x thumb
I know this is old but to tie up what Zach was saying with how this ended is that, in the DE org it looks like you might be able to do multiple overrides, but once the package is installed it looks like Zach's comment about not being able to do multiple will apply.
Photo of Anna Wiersema

Anna Wiersema

  • 10,910 Points 10k badge 2x thumb
Implemented! Let me know how it looks... I tried to be as straightforward as possible (thank you, Zach)  The main change is the section Special considerations for managed packages.
Photo of mB Pat Vachon

mB Pat Vachon, Champion

  • 43,156 Points 20k badge 2x thumb
Can page assignments still be used?
Photo of Anna Wiersema

Anna Wiersema

  • 10,910 Points 10k badge 2x thumb
Yes! There are so many permutations! On that bright shiny future day when we overhaul documentation, this will be presented in a better manner.  In the mean-time, I'm adding it to that tutorial.  

For now, the best tutorials for page overrides (in terms of getting a broad scope of what you can do) are the overview/ cheat sheet and the one on the skuid:page component  one (you may have already realized this).