Data Import Wizard match by Name doesn't work when Name field is encrypted with Deterministic Case Sensitive or Insensitive
Trailblazer Community

Known Issues · No Fix

Data Import Wizard match by Name doesn't work when Name field is encrypted with Deterministic Case Sensitive or Insensitive

Platform Encryption , Data Import Wizard

Last updated 20 days ago ·Reference W-7890661 ·Reported By 4 users

No Fix

Summary
When the standard Name field on an object is encrypted with Platform Encryption Deterministic schema, Data Import Wizard (DIW) should be able to match existing records with Name or Name+Site for Account as an example.

However, despite the import showing as successful the records are not actually processed by the import wizard.

While matching the CSV data against the Name data, the CSV data is text, but the actual record data is encrypted text at the database level. Due to this inconsistency, DIW is unable to identify the corresponding account ID and the operation is ignored.

Repro
Prerequisites:
- Create an Account record with the following details.
Name: LeadImportTestAccount
Account Site: Headquarters
- Enable Shield Platform Encryption
https://trailhead.salesforce.com/en/content/learn/modules/spe_admins/spe_admins_get_started
- Enable "Deterministic Encryption" in Setup > Platform Encryption > Advanced Settings
- Choose Tenant Secret Type: Data in Salesforce (Deterministic) and "Generated Tenant Secret"
- Encrypt the Account Name Standard Field with Encryption Scheme: Deterministic - Case Insensitive or Sensitive
- Gather Statistics and Sync to encrypt the existing record's Name.

Steps to reproduce existing Account not being updated when using Name as matching criteria via DIW:

1. Create a CSV with the following columns populated:

Account Name: LeadImportTestAccount
Account Site: Headquarters
Account Description: If this is showing in the Account Description Field the Update was successful.

2. Navigate to the Data Import Wizard and Launch Wizard!

3. Make the following selections for the each step:

A) What kind of data are you importing?: Account and Contacts

B) What do you want to do?: Update existing records

Match Account by: Name & Site
Update existing Account information: Checked

C) Where is your data located?: CSV and select the file you created in step 1.

4. Check to ensure the columns in the CSV are properly mapped to the Account: Account Name, Account: Account Site, Account: Description fields and click Next and then Start Import.

Actual Results: On reviewing the BULK job results, they show that the update operation was successful however, on reviewing the Details tab of the only matching Account record you will find that the Detail field was not populated with the value contained in the update file, "If this is showing in the Account Description Field the Update was successful."

Expected Results: Matching the existing Account based on Name field would properly update the record when Deterministic encryption is enabled on the Account Name field.


Steps to reproduce Custom Lookup field not being properly populated when using Name as matching criteria for related Account record on Lead creation via DIW:

1. Created a new custom lookup field to Account on the Lead object with Field Label: RelatedAccount

2. Create a CSV file for Lead Import with the following columns populated

Name: Test Lead
RelatedAccount: LeadImportTestAccount
Company: LeadImportTest

3. Launch the Data Import Wizard and choose the following selections:

A) What kind of data are you importing?: Leads

B) What do you want to do?: Add new records

Which Account field in your file do you want to match against to set the RelatedAccount lookup field?: Account Name

C) Where is your data located?: Select the CSV from step 2.

4. Ensure the columns your CSV are mapped accordingly and Start the Import.

Actual Result: The operation shows as successful however, the custom lookup field (RelatedAccount) is not properly populated on the newly created Lead record.

Expected Result: If using Name as matching criteria is a limitation of Shield Platform Encryption and the matching related records by Name via Data Import Wizard, it would be documented or if this should work, the import would be successful.

Workaround
Match based on other criteria such as Salesforce Record Id or consider disabling encryption on the target object's Name field.

Reported By (4)

Marek Żybura Shannon Anglero Leo Moreno Sandeep Nehra

Is it Fixed?

AP0 AP3 AP4 AP5 AP6 AP7 AP8 AP9 AP10 AP11 AP12 AP13 AP14 AP15 AP16 AP17 AP18 AP19 AP20 AP21 AP22 AP24 AP25 AP26 AP27 AP28 AUS14S AUS18S AUS16S AUS13 AUS11 AUS1 AUS28S AUS20S AUS27 AUS26S AUS25 AUS24S AUS23 AUS22S AUS2S AUS36S AUS38S AUS3 AUS4S AUS47 AUS43 AUS5 AUS6S AUS7 AUS79 AUS77 AUS75 AUS9 BRA1 BRA2S BRA3 BRA4S BRA5 BRA6S BRA8S CAN1 CAN17 CAN11 CAN25 CAN2S CAN20S CAN29 CAN28 CAN27 CAN26 CAN31 CAN4S CAN6S CAN8S CS1 CS2 CS4 CS5 CS6 CS7 CS8 CS9 CS10 CS109 CS108 CS107 CS106 CS105 CS102 CS101 CS100 CS115 CS119 CS110 CS117 CS114 CS113 CS112 CS111 CS11 CS116 CS123 CS122 CS121 CS126 CS127 CS129 CS128 CS125 CS124 CS137 CS138 CS133 CS132 CS14 CS148 CS142 CS159 CS152 CS151 CS15 CS162 CS167 CS166 CS16 CS169 CS165 CS160 CS173 CS17 CS172 CS170 CS171 CS174 CS18 CS189 CS194 CS192 CS193 CS190 CS191 CS199 CS197 CS19 CS198 CS196 CS195 CS20 CS209 CS200 CS202 CS201 CS203 CS21 CS219 CS218 CS217 CS216 CS215 CS214 CS213 CS212 CS211 CS210 CS22 CS220 CS226 CS224 CS222 CS225 CS223 CS221 CS23 CS234 CS24 CS25 CS26 CS27 CS28 CS29 CS308 CS31 CS32 CS33 CS34 CS35 CS36 CS37 CS40 CS41 CS42 CS43 CS44 CS45 CS47 CS53 CS57 CS58 CS59 CS60 CS61 CS62 CS63 CS64 CS65 CS66 CS67 CS68 CS69 CS72 CS73 CS74 CS75 CS76 CS77 CS78 CS79 CS80 CS81 CS84 CS86 CS87 CS88 CS89 CS90 CS91 CS92 CS94 CS95 CS96 CS97 CS98 CS99 DEU10S DEU13 DEU11 DEU1 DEU16S DEU14S DEU12S DEU2S DEU20S DEU25 DEU36 DEU3 DEU38 DEU4S DEU5 DEU6S DEU8S EU16 EU17 EU18 EU19 EU25 EU26 EU27 EU28 EU29 EU30 EU31 EU32 EU33 EU34 EU35 EU36 EU37 EU38 EU39 EU40 EU41 EU42 EU43 EU44 EU45 EU46 EU47 EU48 FRA12S FRA19 FRA1 FRA11 FRA24S FRA2S FRA32 FRA36 FRA34 FRA4S FRA5 FRA6S FRA7 FRA8S FRA9 GBR1 GBR2S GBR4S IND14S IND17 IND19 IND18S IND16S IND15 IND13 IND11 IND1 IND12S IND10S IND20S IND27 IND25 IND21 IND23 IND2S IND28S IND26S IND24S IND22S IND37 IND3S IND39 IND41 IND47 IND4S IND43 IND5 IND6S IND7 IND8S IND9 JPN18S JPN12S JPN10S JPN1 JPN19 JPN17 JPN20S JPN2S JPN21 JPN28S JPN24S JPN22S JPN3 JPN4S JPN5 JPN6S JPN7 JPN8S JPN93 KOR1 KOR2S KOR4S NA104 NA107 NA109 NA100 NA101 NA103 NA102 NA105 NA119 NA116 NA110 NA118 NA112 NA111 NA115 NA114 NA113 NA117 NA125 NA124 NA122 NA120 NA126 NA127 NA123 NA129 NA121 NA128 NA138 NA134 NA133 NA136 NA135 NA132 NA131 NA130 NA137 NA139 NA140 NA142 NA141 NA149 NA146 NA147 NA148 NA154 NA158 NA159 NA153 NA151 NA155 NA152 NA150 NA156 NA161 NA163 NA167 NA160 NA166 NA165 NA169 NA164 NA168 NA162 NA172 NA170 NA174 NA171 NA173 NA196 NA207 NA204 NA206 NA208 NA209 NA21 NA218 NA214 NA217 NA215 NA211 NA212 NA213 NA210 NA219 NA220 NA70 NA71 NA75 NA80 NA81 NA82 NA83 NA84 NA85 NA89 NA90 NA91 NA92 NA93 NA94 NA95 NA96 NA97 NA98 NA99 SGP10 SGP1 SGP2S SGP3 SGP4S SGP5 SGP6S SGP8S SWE1 SWE2S SWE4S UM1 UM2 UM3 UM4 UM5 UM6 UM7 UM8 UM9 USA194S USA13 USA198S USA196S USA1 USA19 USA17 USA15 USA20S USA26 USA28S USA2S USA22S USA3S USA32S USA30S USA36 USA34 USA59 USA60S USA61 USA62S USA7 USA8S

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.