When I try to upload a change set which includes recently changed or newly created classes(which will in the latest API version), it throws an error message saying that the API versions of some components are not compatible with the production one and I need to downgrade it everytime(currently from 30 to 29).

I understand the problem and for the moment doing this workaround. But I need to know why the production is in an older version? Is this problem is upto my manager? Not only in change set uploading but in building managed package and some other tasks as well this is happening.
Please help me to understand this correctly.

NOTE : Found a kind of similar post here but didn't try to hijacking it since it's somewhat older one.


At this time the new SF version (Spring '14) is in its release process. Production environments are always upgraded later than sandboxes. So at this time, the sandboxes are often already on the new version, while Production is still on Winter '14.

In this particular release, there is an extra delay in the production deployment. You can find the full schedules here: http://blogs.salesforce.com/company/2014/01/salesforce-spring-14-release-dates.html

  • So the answer to my question is what I'm currently doing is correct? We have to downgrade them manually where it's required until the final release will take place.
    – highfive
    Mar 25 '14 at 11:01
  • To prevent downgrading, you can do the following: make a new clone of the change set and directly upload it to production (without first uploading to a sandbox). Then it will work without requiring to downgrade. Mar 25 '14 at 12:31
  • That's what I'm doing actually. I got confuse a little with your answer also. My problem is production is v29 and sandbox is v30. But in your answer you are saying "Production environments are always upgraded later than sandboxes". The shared link also saying that Production will be upgraded at last. Have my admin missed something?
    – highfive
    Mar 25 '14 at 13:40
  • I'm not sure I understand. Sandbox is already upgraded and is on v30. Production is upgraded later and therefore is still on v29. What part is confusing you? Mar 25 '14 at 13:43
  • Yeah, that's my observation too and because of this I have to do whatever I have mentioned. I'm asking whether there is an alternative for this or am I missing something.
    – highfive
    Mar 25 '14 at 13:57

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.