Print this page

Change Set Error: "This change set requires the (version number) or later platform version."

Knowledge Article Number 000181707
Description


Issue: You may receive this message while trying to upload a change set:

"This change set requires the (API version number) or later platform version.
One or more of the listed organizations is on a version incompatible with this change set.  You can only select an organization for upload that is running the required version or later."

Reason this occurs: The target org is selected the first time a user uploads a change set.  Based on the target org, Salesforce sets the version of the change set (current release vs next release) to match the target org's version.  Once this is done, Salesforce requires that subsequent uploads of that change set be targeted to other orgs on the same version, or a later (newer) version, used in the original upload. 

Examples:

1.

  • Change Set "A" is created in a Winter '13 org
  • The first upload attempt of Change Set "A" targets a Winter '13 org and is successful
  • A second upload attempt of Change Set "A" targets a Spring '13 org and is successful
  • Both attempts were successful since the first upload attempt locked the change set to Winter '13.  Subsequent upload attempts of the original change set must be targeted to other Winter '13 or Spring '13 orgs based on the "Reason this occurs:" wording above.


2.

  • Change Set "A" is created in a Winter '13 org
  • The first upload attempt of Change Set "A" targets a Spring '13 org and is successful
  • A second upload attempt of Change Set "A" targets a Winter '13 org and hits the error
  • It's expected that the second upload failed since the first upload targeted a Spring '13 org.  Subsequent upload attempts of the original change set must be targeted to other Spring '13 orgs based on the "Reason this occurs:" wording above.
Resolution  


Workaround for Example 2:

  • Clone Change Set "A"
  • Upload of the cloned change set to a Winter '13 org (Example 2 above) is successful
  • Why does the act of cloning the change set resolve the issue?  A cloned change set is treated as a new change set.  Since it has yet to be uploaded to an org, it's version hasn't been locked (as described in "Reason this occurs:" above).  Therefore, it can be uploaded to a current version or a Preview sandbox.    




promote demote