Issues With Managed Package Upgrade

I released managed version of my package say 1.0 with some changes and now I have released another version say 1.1 with some changes in existing components which were present in V 1.0, but few of them aren’t upgraded with new version

Here are the details:-

  • I created a Lightning Application with name say “Lightning
    Application” in V 1.0 , now I edited the name with Label say
    “Lightning Only” (API Name begin same), I was considering it should
    be upgraded with label “Lightning Only” but it didn’t.
  • I created a custom object tab in V1.0 and later in V 1.1 I added custom logo for that tab, I thought new logo will be reflected on custom object tab when package is upgraded , but it didn’t.(I have added logo in Document and that is available in package)

    However when I am installing V1.1 in fresh org (Not Upgrading the existing package) these changes are reflecting as they should be, aren’t these two things mentioned above are up-gradable?

(I was checking Components Available in Managed Packages for reference.)


After installation the subscriber org can update certain component attributes. For instance, with a tab they can edit the Tab Style. Subsequent package upgrades won’t overwrite these attributes to avoid changing what the subscriber could have customized.

See Editing Components and Attributes After Installation in the ISFforce Guide for what is and isn’t subscriber and developer editable.

Idea provided by Nachiket: Option To Override Components and Attributes During Package Upgrade

Source : Link , Question Author : Nachiket Deshpande , Answer Author : Daniel Ballinger

Leave a Comment