Encrypted Custom Field Stored Values
As of 2014.1, a Use Encrypted Format option is available for new custom field definitions with specific text types. When Use Encrypted Format is enabled, field values are encrypted in the database. (Values are still displayed in the user interface.)
After you save a custom field definition, you can't change the Use Encrypted Format setting.
When you specify that a field be encrypted, any value in the encrypted field displays as ENCRYPTED in all accounts except the account where the value was first created.
The encrypted format option isn't supported for Transaction Item Option, Suitelet, Workflow, or Workflow State custom field definitions. For custom field definitions where it's supported, the encryption format option defaults to disabled.
You can encrypt the following text types:
-
Email Address
-
Free-Form Text
-
Long Text
-
Phone Number
-
Rich Text
-
Text Area
For all other text types, the Use Encrypted Format box isn't available.
Be aware of the following precautions for fields with encrypted stored values:
-
Fields with encrypted stored values aren't available to reporting, SuiteAnalytics Connect, or for sourcing or filtering. Other than the Rich Text and Long Text text types however, they can be returned in the results of searches and saved searches.
-
The nlapiLookupField SuiteScript API doesn't work for fields with encrypted stored values. Other SuiteScript APIs that rely on search may not be supported.
-
Encryption of stored field values increases their size and can have performance implications.
-
You can't change the data type of a field with encrypted stored values to one that doesn't support encrypted store values.
For security reasons, system notes for fields with encrypted stored values mask old and new field values, displaying asterisks only.