Background
- We actually have people whose legal name is “Null”. To distinguish this from database NULL, we send it as the quoted string "Null".
- The value stays as "Null" in a custom object, but when we use Load to People to write into the Person object, it becomes a blank (null).
Quick repro
- Source sends LAST_NAME as the string "Null" (double-quoted), not DB NULL.
- It lands in a custom object as "Null" correctly.
- Load to People into Person → LastName ends up blank.
Current vs expected
- Current: Load to People treats the string "Null" as null and clears the field.
- Expected: Keep the literal "Null" as text, or give us a toggle/setting to treat "Null"/"NULL"/"null" as strings while only true empty/DB NULL becomes null.
Why it matters
- Real names get wiped, which hurts data quality and user trust.
- Workarounds like inline editing or replacing with “N/A” don’t scale and aren’t appropriate for legal names.
Ask
- Could you enhance Load to People to preserve quoted strings like "Null" for Person fields, or provide an option to do so?
- Support confirmed this behavior and suggested inline edit as the only way to store "Null" as text; has anyone found a better workaround?
Thanks, and appreciate any upvotes or guidance!