1

I have a managed release package at version v1. I added a new tab in version v2 and upgraded the package. After installation of this upgraded package, the new tab is not visible for the app. I checked my custom app and see that the new tab is not included in the list of included-tabs. However, when I created the upgrade package, I had added it to the App.

To make the tab visible, I had to manually include the tab in the test-org.

Does this mean if I add a new tab during upgrade, all the subscribers would have to manually include the tab in their respective orgs? Is this the desired behavior? Am I missing something?

Improve this question

1 Answer 1

Reset to default
3

Applications are now upgradeable as part of a package upgrade. It is always important that you check the documentation to ensure that you have the most recent information on packaging behavior before making any assumptions.

Original Answer

That's correct. System administrators can customize the app after installation, so the system will not upgrade the app because it may override any customizations the system administrators may have made. There are a few elements like that, such as page layouts, list views, and email templates. See Components Available in Managed Packages for a full list of objects. The first column next to the component type will say "Yes" if the component is updated during upgrades, or "No" if not.

Improve this answer
5
  • @sfdcfox but Application says Yes in the first column, am I looking at the wrong listing?
    – Phil B
    Nov 28, 2018 at 21:49
  • 1
    @PhilB This answer was correct at the time. See this link.
    – sfdcfox
    Nov 28, 2018 at 23:24
  • @PhilB Also, you might want to check/test this to be sure. There have been a number of ... interesting documentation bugs recently.
    – sfdcfox
    Nov 28, 2018 at 23:27
  • @sfdcfox the functionality appears to be the same, adding a tab to the packaged app does not come through in upgrades, curious that the documentation does not reflect that anymore.
    – Phil B
    Nov 29, 2018 at 14:49
  • @PhilB So... another documentation bug, maybe? Perhaps someone needs to open a case with support?
    – sfdcfox
    Nov 29, 2018 at 14:50

You must log in to answer this question.

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