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.)

  • As subscriber can change these details as well. So I think SF does not allow them to overwrite again. Thats why your changes doesn't reflect in old org. – Tushar Sharma Oct 24 '17 at 9:39
  • @TusharSharma yeah that was my thought as well , but if these are part of package then upgrading these changes might not affect subscriber just a thought. – Nachiket Deshpande Oct 24 '17 at 9:42
  • 1
    if subscriber has changed the details then your upgrade will override his changes. Thats why SF don't push your changes or let subscriber decide. – Tushar Sharma Oct 24 '17 at 10:24
  • 1
    @TusharSharma Agreed !! or if SF could add option to let subscriber deiced whether they want to override changes or not during package upgrade may help in such scenarios. – Nachiket Deshpande Oct 24 '17 at 10:29

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


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.