[BUG] - Lead Matching Custom Metadata Field Updates not working

[rdblake21]

Describe the bug When setting up Lead Matching, the Creation and Matching of Lead records works as expected. However, when trying to setup the Custom Metadata Type, to allow for custom fields to be mapped to the Lead Record, the fields don't populate or move data that isn't in the standard list of expectations. In this case, we're unable to capture Program or Lead Source information.

To Reproduce Steps to reproduce the behavior:

1. Setup Contact Matching on any event to skip creating a contact
2. Setup Lead Matching on the same event to create a New lead
3. Leverage a field that isn't a part of core mapping cabilities, like "Title" as well as a Hardcoded value of "LeadSource"
4. Submit the registration as a net new individual, see the lead is created and that the mapped field values don't get carried over.

Expected behavior The expectation is that when a field is mapped in Custom Metadata type, it's grabs the values from the Summit Event Registration record and puts them on the Lead field.

Screenshots Ryan Blake tested this, in great length, and was getting the issue above as well.

Additional context In an effort to try and use Flow to mitigate this issue, Flow wasn't able to handle this experience either. I created three different flows to try and mitigate this.

• Flow 1: On a newly created Summit Event Registration, if the Lead is New or the Lead field has a value, update the related Lead Record. In Flows Debug, this works as expected. When you Clone the Summit Event Registration, it works as expected. But when you submit the registration from the form/website, it doesn't fire. System Debug shows the flow fires, but nothing transpires.
• Flow 2: On a new created Lead Record or updated Lead record, find the matching Summit Event Registration record and update the mapped values (from in the flow). In Flows Debug, this works as expected. When you Clone the Summit Event Registration, it works as expected. But when you submit the registration from the form/website, it doesn't fire. System Debug shows the flow fires, but nothing transpires.
• Flow 3: Update a checkbox on the Summit Event Registration record to TRUE. Another flow to then look at that value to fire another flow to update the Lead Record associated to the Summit Event Registration. The initial flow never fires to update the Lead record, so that checkbox stays as False.

Ideally, would like to understand why the Custom Metadata Types isn't working as expected.