![]() Then you can decide what to do with the non-compliant addresses. If any row fails with the email validation error, you just skip it. ![]() If this is a one-time dataload, run a separate process that, for every row in SFDC with this custom field populated, attempts to copy the contents of this custom field to the native email field. ![]() In your initial data integration from the external application, map the email field that you describe into a new (non-email, just text 255) custom field in SFDC. The quickest path to success that I would suggest would be this: I've looked previously and not been able to find a definitive answer on exactly which rules SFDC applies to the native "Email" field type.
0 Comments
Leave a Reply. |