Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
What’s a Package?
Comparison of 2GP and 1GP Managed Packages
Namespaces
Package IDs and Aliases
Before You Create Second-Generation Managed Packages
Workflow for Second-Generation Packages
Configure Packages
Project Configuration File for Packages
Keywords
Package Installation Key
Customize Package Installs and Uninstalls Using Scripts
Share Release Notes and Post-Install Instructions
Specify Unpackaged Metadata for Package Version Creation Tests
Override Translations in Second-Generation Managed Packages and Unlocked Packages
Best Practices for Second-Generation Managed Packages
Frequently Used Packaging Operations
Create a Package
Push a Package Upgrade
Install a Package
Uninstall a Package
Publishing Your App on AppExchange
Gaps Between First-Generation and Second-Generation Managed Packaging
Test and Respond to the New Order Save Behavior
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Override Translations in Second-Generation Managed Packages and Unlocked Packages

You can override metadata translations for custom objects in namespaced unlocked packages and second-generation managed packages. For example, override the label on a custom field or workflow task.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Professional, Enterprise, Performance, Unlimited, and Developer Editions

User Permissions Needed
To override metadata translations: View Setup and Configuration

AND

Customize Application

Overriding translations in second-generation managed packages and unlocked packages has limitations:

  • You can’t override translations for standard objects in packages.
  • You can’t override data translations.

Note

If you installed a managed package that includes translations, those translated values appear to users regardless of whether the language is active on the Translation Language Settings Setup page. Before you can override those translations, you must select languages for your org and enable Translation Workbench.

  1. From Setup, in the Quick Find box, enter Override, and then select Override.
  2. Select the Package that you’re overriding.
  3. Select the Language that you're entering your overrides in.
  4. Select a Setup Component. See Metadata Available for Translation for a list of translatable components.
  5. Depending on the setup component, select the next options.
    The aspect is a part of the setup component that you can translate. For example:
    • Workflow tasks have an object (for example, Account or Contact) and aspect (Subject or Comment).
    • Custom Report Types have a custom report type entity (Custom Report Type, Custom Report Type Column, or Custom Report Type Layout Section) and aspect (field label or description).
    • Flows have a flow type (Flow and Autolaunched Flow), a flow name, and a flow component (Definition, Version, Screen Info, Screen Field, and Choice). Flow components can have a flow version, screen, or aspect.
    For global value sets and picklist values, you can translate inactive values by selecting Show Inactive Values.
  6. To enter new values, double-click in the translation column. You can press TAB to advance to the next editable field or SHIFT-TAB to go to the previous editable field.

    The Out of Date column indicates the possibility that the term needs translation because the master label has been updated. When editing a button or link label, you see the Button or Link Name column, which is used to refer to the component when using SOAP API.

    Note

  7. Click Save.