0

I am trying to encrypt field Lead.Name but it fails due to:

Encryption can't be enabled for fields referenced in the custom formula fields: Lead.Data Quality Description.

I checked this formula field and all functions are allowed as listed here: documentation This is the definition of the text formula field:

IF(
    Data_Quality_Score__c = 100,
    "All Lead Details Captured", 
    "Missing: " & 
        IF( 
            ISNULL(FirstName),
            "First Name, ",
            ""
        )
    & "" & 
        IF(
            ISNULL(LastName),
            "Last Name, ",
            ""
        )
    & "" &
        IF(
            ISNULL(Company),
            "Company, ",
            ""
        )
    & "" &
        IF( 
            ISNULL(Phone),
            "Phone, ",
            ""
        )
    & "" &
        IF(
            ISPICKVAL(Salutation, ""),
            "Salutation, ",
            ""
        )
    & "" &
        IF(
            ISPICKVAL(Rating, ""),
            "Rating, ",
            ""
        )
    & "" &
        IF(
            ISNULL(City),
            "Complete Address, ",
            ""
        )
    & "" &
        IF(
            ISNULL(Email),
            "Email",
            ""
        )
)
3
  • The = operator is not in the list. Have you tried removing it?
    – manjit5190
    Commented Jun 9, 2021 at 14:48
  • Can you remove the field from the formula and then encrypt the field? After this, I believe you should be able to use it back in the formula. Recommend reviewing help.salesforce.com/… Commented Jun 9, 2021 at 16:52
  • N.B. you can replace all the "" with NULL and the concatenation works as expected; I agree with Swetha -- I had similar issue and had to encrypt first, then create the formula.
    – cropredy
    Commented Jun 9, 2021 at 23:03

1 Answer 1

0

So manjit5190 was right. Using the = operator was the issue. The referenced field Data_Quality_Score__c used in the formula has been encrypted as well and therefore the problem using the = sign. Unfortunately, I did not find a workaround for this, so this Lead.Name field won't be encrypted.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .