... a contemporary perspective on how to integrate B2C Commerce and the Salesforce Customer 360 Platform to power frictionless customer experiences in the B2C domain.
When deploying PersonAccounts -- the Contact: B2C Commerce: Standard Person Accounts duplicate rule's fieldMappings can sometimes be rendered out of order. This seems to be a bug with the platform, as the meta-data mapping definition doesn't deviate from the format used for the Contact duplicate rule.
Incorrect Field Mapping Order
In this image the fields are in the wrong order; they should be rendered in the following order.
Correct Field Mapping Order
As of this writing, there is no fix for this issue. The issue seems to occur intermittently and inconsistently. Thankfully, this issue can be resolved manually by adjusting the field mappings.
Scroll down the bottom half of the display and find the Conditions Heading. The mapped fields should be visible underneath this heading.
Update the field mappings so to reflect the following fields in this order:
B2C Customer ID not equal to
B2C CustomerList ID not equal to
B2C Customer No not equal to
EmailAddress not equal to
LastName not equal to
B2C CustomerList ID equal to
The first five fields should be set to not equal to an empty string. We want these field mappings to evaluate fields where these values are populated. For the last field (B2C CustomerList ID) -- we want this field mapping to evaluate when the field is not populated.
Ensure the filter-logic field contains the following fieldMapping rules logic:
1 OR (2 AND 3) OR (2 AND 4 AND 5) OR (2 AND 4) OR (4 AND 5 AND 6)
The filter logic defines in what sequence filters should be processed -- and maps the fieldNumber (ex. 1, 2, 3, etc.) to the fields described above. Another way to think about this filter logic is:
First match on B2C Customer ID for fields that are not null
Then match on B2C CustomerList ID and B2C Customer NO for fields that are not null
Then match on B2C CustomerList ID, Email, and LastName for fields that are not null
Then match on B2C CustomerList ID and Email for fields that are not null
Lastly match on B2C CustomerList ID, Email, and LastName where Email and LastName are not null and B2C CustomerList ID is null
The combination of the fieldMappings and filter logic is how duplicate rules evaluate matches. Customers can extend the rules by adding new fields and filter logic conditions to the rules definition.
Issue Summary
When deploying PersonAccounts -- the Contact: B2C Commerce: Standard Person Accounts duplicate rule's fieldMappings can sometimes be rendered out of order. This seems to be a bug with the platform, as the meta-data mapping definition doesn't deviate from the format used for the Contact duplicate rule.
Incorrect Field Mapping Order
Correct Field Mapping Order
As of this writing, there is no fix for this issue. The issue seems to occur intermittently and inconsistently. Thankfully, this issue can be resolved manually by adjusting the field mappings.
Issue Resolution Instructions
ConditionsHeading. The mapped fields should be visible underneath this heading.not equal tonot equal tonot equal tonot equal tonot equal toequal toThe filter logic defines in what sequence filters should be processed -- and maps the fieldNumber (ex. 1, 2, 3, etc.) to the fields described above. Another way to think about this filter logic is:
Savebutton to save your changes.