Loading

Package upgrade breaks translation for global value set

Publish Date: Apr 29, 2026
Description

Create a managed package with translations for the global value set.

  1. On a Developer org, create a Global Value Set.
  2. Add a few picklist values to the GVS.
  3. Create a Custom field on any Standard/Custom object using the Global Value Set.
  4. Add the GVS to a package and upload the package.
  5. Install the package on a subscriber org.

After installing the package in the subscriber org upgrade the package to validate the behaviour by following the below steps

Reproducible Steps:

  1. Navigate to: Setup → Translation Workbench → Translate
  2. Select:
    1. Language: Select the translated language while creating package
    2. Component: Global Value Set
  3. Locate:
    1. Global Value Set: 
    2. Value: Picklist value
  4. Update translation label to: package translation value or custom translation value→ Save
  5. Upgrade package (same or higher version)
  6. Update translation 'picklist value' value to: Blank → Save

    It will be enforced with package translation value rather than Blank as we updated in the previous step.
Resolution

As a workaround, if there is a requirement to set the translation value to blank (null), it is recommended to update the translation value to null again after the package upgrade.

It has been observed that the override occurs on the first null update following the upgrade, and subsequent updates to set the value to blank are retained as expected.

 
Knowledge Article Number

005321484

 
Loading
Salesforce Help | Article