8

I was tasked with adding an app from the app exchange. As part of that process, I need to create a new trigger in the sandbox, and then move that to production via a change set. However, when I try to upload that to production, I'm getting an error:

error All components failed Version Compatibility Check. Every component in this change set requires the "29.0" or higher platform version. Please select an organization with a platform version of "29.0" or higher.

Looks like my production version is 28.0, but sandbox is 29.0.

What's the best course of action here? Should I update production? If so, how do I do that?

  • Couldn't you just change the metadata for the trigger to v.28? are you using any syntax specific to v29? – Phil B Oct 3 '13 at 17:46
  • Looks like that would work as well, phil. I got that answer elsewhere and applied it. – Geoff Maddock Oct 3 '13 at 19:29
  • Phil, do you want to re-post your comment as an answer, to make it easier to find for future visitors with the same questions? – Benj Oct 3 '13 at 20:42
5

You're smack in the middle of a release cycle for the Winter '14 release of Salesforce, which brings version 29.0 of the API. Sandboxes are typically upgraded at least a month in advance of the production release, which is why your code in the sandbox is on version 29.0. You can choose your API version however on your metadata components. You have two options:

1) roll back your code to version 28.0 of the API to deploy now.

2) Wait for your instance to be upgraded to Winter '14, either this weekend or next weekend. The release schedule can be determined for your server at http://trust.salesforce.com/

| improve this answer | |
  • 4
    It's worth noting that if you follow the Sandbox Preview instructions, you can avoid this hassle and keep your Sandbox on the same version as your production environment. Also, of course, this is only a problem for approximately 25% of the year (depending on the number of releases in a year) if you do use the Sandbox Preview. – sfdcfox Oct 3 '13 at 18:03
3

Solution copied from another answer since this question ranks highest in Google for the error and we're in the midst of the Winter release.

I've just amended the trigger. Go to Setup> Develop> Apex Triggers>(SelectTrigger) Edit> Click Version Settings> Change Version to 32.0> Save. Deployed Successfully

Source: Changeset Error

| improve this answer | |
0

in sandbox go to your trigger and click edit go to version settings tab in Salesforce.com API select the version you are running in Production hit save move change set.

| improve this answer | |

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.