function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
GoForceGoGoForceGo 

Pushing Managed Package Upgrades

 

We have a lot of customers on different versions of our package - this was before patch upgrades were available.

 

I would like to "push" the latest version to everyone, assume that everything is backward compatible.

 

I am wondering whether I can do the following:

 

1. Create a patch upgrade to our latest package say 1.45 - so the patch version would be 1.45.1

2. Push 1.45.1 it to all customers that might be on 1.25 or 1.34 or 1.45.

 

Note that we have added new fields/classes/vf pages. So customers with 1.25 or 1.34 should get these new components.

 

The documentation says that push upgrades can be sent to all customers with same major release - i.e 1.x version, but not 0.x version . So seems like it can be done. But patch releases cannot add new components according to documentation as well...

 


Also, do I need to know all the subscribers or salesforce knows automatically? Is there any depedency on LMA - i.e it knows only subscribers only after LMA was installed in some other org?

 

 

 

 

 

 

 

A_SmithA_Smith

This isn't possible today.  You can only upgrade customers of the same core release with a patch.  Can't go back to other major releases. 

GoForceGoGoForceGo

Thanks Andrew.


The doc says:

 

Only subscribers running the same Major Release or subsequent patch to that release are eligible to receive a patch for that Major Release using push upgrades. Thus, a subscriber can't go from version 1.0 of a package to version 2.0.1 using a push upgrade.

 

The doc seems to be implying it can be done since we never went to 2.0 i.e a 1.35 customer could get a patch upgrade 1.45.1.

 

Is the doc not accurate? Or perhaps the doc needs to add a caveat that  you could go from 1.35 to 1.45.1 as long as the restrictions for patch release (i.e no new components, no deleted components etc) are respected.

 

 

 

 

 

 

 

G2WIntegrationG2WIntegration

btw-Push Major should now be enabled to allow going from 1.0 to 2.0 (or maybe only to 2.1, but we haven't been able to figure it out yet (our question on that thread here)

http://boards.developerforce.com/t5/General-Development/Push-Major-Upgrade-doesn-t-seem-to-be-enabled/m-p/508951

 

Doc on push major (pg 197):

https://na1.salesforce.com/help/doc/en/salesforce_winter13_release_notes.pdf

 

and here:

http://developer.force.com/releases/release/Winter13/PUSH+Major+Upgrade