+ Start a Discussion

picklist values on upgrade managed package

we created a managed package where we also deliver picklist values to a global picklist which is included in the package.
After we deployed this package on a subscriber org and on the subscriber org, we added new picklist values and disabled some values which came with the package in the mentioned global picklist.
On upgrading the manage package, all changes made on the subscribe for this global picklist is gone.

If I understand this description correctly: https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/packaging_component_behavior.htm

Picklist Values
Subscribers can rename or delete picklist field values. Carefully consider this when explicitly referencing a picklist field value in Apex.
Picklist field values can be added or deleted in the developer’s org. Upon upgrade, no new values are installed. Values deleted by the developer are still available in the subscriber’s org until the subscriber deletes them.

So this should not happen, right ?
Don Schueler 6Don Schueler 6
The way I read this and my experiece is that once a managed package is installed....pushing and upgrade will not add or delete any picklist items. I think it all has to be done manually.
Don Schueler 6Don Schueler 6
p.s. I believe some have used the Metadata API to do some things here..but I am not aware of anything generic
Rick RoseRick Rose
I have experienced the same thing and I dont remember it happening in the past. I am wondering if it is because I am using a managed picklist value set? 

Values that have been added are not deleted, but values that were deactivated are brought back with each upgrade. 
Sahar SabinSahar Sabin
Hey, we encountered this problem while adding a new field into our package.
This is Salesforce official comment:
"Yes, as mentioned by you it is a limitation. Any new packaged picklist values will need to be either manually added after the upgrade or created via a postinstall script with the Metadata API."