Deploy Applications with Shield Platform Encryption Enabled
As a developer, you can deploy applications to your org by using tools such as
Salesforce Extensions for Visual Studio Code, Migration Tool, and Postman. When you deploy your
application, the setting of the Encrypted Field attribute is determined by its setting in the
target org.
Required Editions
Available in both Salesforce Classic (not available in all orgs) and Lightning
Experience.
Available in: Enterprise, Performance, and Unlimited
Editions with the Salesforce Shield or Shield Platform Encryption licenses.
Available for free in Developer Edition.
Note This page is about Shield Platform Encryption,
not Classic Encryption. What's the difference?
Use this table as a guide when deploying your application between orgs with different Shield
Platform Encryption settings.
Source Organization
Target Organization
Result
Shield Platform Encryption enabled
Shield Platform Encryption enabled
The source Encrypted field attribute indicates enablement.
Shield Platform Encryption enabled
Shield Platform Encryption not enabled
The Encrypted field attribute is ignored.
Shield Platform Encryption not enabled
Shield Platform Encryption enabled
The target Encrypted field attribute indicates enablement.
Note The setting of the Encrypted Field attribute in the target org is the one
that's honored.
You can also deploy Shield Platform Encryption by using the PlatformEncryptionSettings Metadata
API. Regardless of how you deploy, Salesforce automatically checks to see if the
implementation violates Shield Platform Encryption guidelines.
Note Salesforce doesn’t impose a hard limit on the number of fields that
you can encrypt, but there is one functional limitation. If you have Shield Platform
Encryption enabled and you want to deploy packages, you can only deploy 80 fields at a time.
If you configure 80 or more fields to encrypt, you must deploy the package in phases. which
include fewer than 80 fields in each one.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.
