Beta packages have severe limitations.

Package is a Beta.

Admin Solution
This is a Beta package, it can't be upgraded without uninstalling and installing the latest version. Avoid installing in a sandbox used in the release pipeline. If uninstalling ensure that there is no custom development that references the beta package components, if there is it must be deleted, the package uninstalled and reinstalled, then re-deployed with any data re-mapped.

Step 1: Evaluate the Impact

Assess how the Beta package is being utilized within your Salesforce org to understand its full impact.

Step 2: Communicate with Your Team

Ensure that all stakeholders are informed about the Beta package's limitations and the upcoming changes.

Step 3: Identify Dependencies

Perform an audit to locate any custom configurations or developments tied to the Beta package.

Step 4: Plan for Data Mapping

Develop a strategy for backing up and remapping any data affected by the package's uninstallation and reinstallation.

Step 5: Test in a Separate Sandbox

Validate your uninstallation and reinstallation plan in a sandbox environment to anticipate any issues.

Step 6: Prepare for Uninstallation

Ready your org for the Beta package's removal, ensuring data backups are complete and users are aware of the timeline.

Step 7: Delete Custom Development References

Remove any custom developments that reference the package before uninstalling to avoid disruptions.

Step 8: Uninstall the Beta Package

Proceed with the careful uninstallation of the Beta package, following Salesforce's best practices.

Step 9: Install the Latest Version

After removal, install the latest version of the package, previously vetted in a sandbox if possible.

Step 10: Re-deploy Custom Development and Remap Data

Redeploy any custom solutions and use your data plan to restore necessary information.

Step 11: Conduct Post-Installation Testing

Thoroughly test your Salesforce org post-installation to ensure functionality and data integrity.

Step 12: Monitor and Provide Feedback

Keep a close watch on the newly installed package version, reporting any issues to the developer as needed.

Developer Solution
This is a Beta package, it can't be upgraded without uninstalling and installing the latest version. Avoid installing in a sandbox used in the release pipeline. If uninstalling ensure that there is no custom development that references the beta package components, if there is it must be deleted, the package uninstalled and reinstalled, then re-deployed with any data re-mapped.

Step 1: Review Package Dependencies

Thoroughly assess the Beta package components and their interdependencies within your org.

Step 2: Communicate with Stakeholders

Keep all relevant stakeholders informed about the upcoming changes and potential impacts.

Step 3: Backup Data and Metadata

Ensure all related data and metadata are securely backed up before proceeding.

Step 4: Isolate Dependent Components

Identify custom components reliant on the Beta package and prepare them for the transition.

Step 5: Test Uninstallation in Sandbox

Conduct a trial run of the uninstallation process in a sandbox to identify any potential issues.

Step 6: Update Custom Code

Refactor or adjust your custom code to ensure compatibility with the new package version.

Step 7: Uninstall the Beta Package

Follow Salesforce best practices to safely uninstall the Beta package from your production environment.

Step 8: Install the New Package Version

Install the latest, vetted version of the package, ensuring it's been tested in a sandbox environment.

Step 9: Re-integrate Custom Developments

Redeploy any custom solutions that were dependent on the Beta package, ensuring they align with the new version.

Step 10: Restore Data

Use your data backup to restore any information affected by the uninstallation and reinstallation processes.

Step 11: Conduct Extensive Testing

Carry out thorough testing to verify that all functionalities perform as expected with the new package version.

Step 12: Monitor and Adjust

Maintain vigilance for any issues post-reinstallation and be ready to make necessary adjustments.

Step 13: Document and Share Learnings

Document the entire process and share insights gained with your team and stakeholders to facilitate future upgrades.

This solution was generated using AI and quality-checked by Hubbl humans.