From the documentation:
When you create a Force.com project, it's designed to work with a specific version of the server. When the server is upgraded to the next version, your projects need to be updated so you can have access to the latest features and metadata
If you don't observe any changes, they were probably just white space changes (e.g. replacing spaces with tabs). Technically, the upgrade process is setting a new API version, refreshing the metadata, then updating any files that are not synchronized with the server. This is usually harmless unless you have data that has not been saved to the server (e.g. ...
Above link provides details about which components are supported in package upgrade. Hope this helps you!
To this problem, Salesforce has provided a button 'Recompile All' on the page where the 'Bad References' error is thrown. I clicked on the button to recompile all the classes and I was able to open my package components without any issues. Thereafter the error isnt thrown and the list of package components open as before.
Once it has been released to production via a managed package my understanding is that it is locked in from that point forward.
You will get an error along the lines of:
Save error: Global/WebService identifiers cannot be removed from managed application: Method: foo bar
There are a couple of suggestions via Remove 'Public and Private' tagging from ...
You will have to uninstall the BETA package and there is no other alternative here.
Things to keep in mind
1.All the new fields you created on the managed objects will have to be deleted to allow uninstall
2.If you have added validation rules ,workflows or any other customization on top of managed package needs to be deleted and recreated
3.You should ...
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 ...
As the error states, you can't remove a design attribute that previously existed in an older version. This is because it could break existing implementations that depend on this attribute. This is similar to how you cannot delete a global class or an unprotected workflow element. These restrictions prevent the system from breaking as a result of an upgrade. ...
The PackageVersionHeader is optional, so you can safely omit it if you aren't using any managed packages or are happy to the the API versions specified when you exported the Enterprise WSDL.
If possible, look to encapsulate all the Salesforce API calls in a single module. Then use that as a single point of interaction between Salesforce and the rest of your ...
I just ran into the same issue. A new picklist value was added to a field and then deployed via a non-beta managed package update.
After the new package was installed the picklist value wasn't present.
The question I have a managed package, if I add values a picklist, will my customers get it on an upgrade? addresses it.
From the current answers, there ...
I would recommend using a tool that get's your org's metadata through the metadata API.
For example if you use eclipse, go to the root of your project, there is a folder that is named "Referenced Packages" open it and there you see all packages installed with their components.
Now - if you use a version control system on your project like git, you can ...
You can create the new version of package and this time it would be Managed Released. This package will contain all the components (new fields) that you had added for Beta package.
You need to uninstall the beta package, if you have installed on some orgs as they won't be upgradable.
After uninstallation, you will be able to install new version of Managed ...
Not all components are upgradable
You can look at the table of this page:
Components Available in Managed Packages
The main reason for that is that these components can be changed on the client's org, therefore cannot be re-changed by upgrading package.