Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrading to 3.119 Fails if Org has pre-existing Unmanaged Custom Tabs on Volunteer Shift / Hours #498

Closed
coriobriensfdo opened this issue Sep 10, 2020 · 2 comments · Fixed by #497

Comments

@coriobriensfdo
Copy link

coriobriensfdo commented Sep 10, 2020

Issue:

Due to Issue #495 , version 3.119 released a managed tab on the Volunteer Shift and Hours objects.

However, if a customer Org has already created their own unmanaged versions of these two object tabs, an error is thrown during upgrade:

Unmanaged custom object tab already exists, package upgrade cannot create another tab
OR
_Cannot add component of type:CustomTab named:Volunteer_Hours__c subjectId:01r5w000001Bt3t to another package because it is an installed component._

Steps to Repeat:

  1. In an org with V4S version 3.118 create a tab for Volunteer Shift and Hours objects.
  2. Using MetaDeploy, attempt to install version 3.119.
    Expected Result: Org updates to 3.119
    Actual Result: Org update fails with above message(s)

Workaround:
Delete custom unmanaged object tabs, and reattempt installation.

Further details found on W-8068273

@salesforce-org-metaci
Copy link
Contributor

Included in beta release 3.120 (Beta 2)

@salesforce-org-metaci
Copy link
Contributor

Included in production release 3.120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant