Right. That is what I suggested. We just need to get the master members Record created if a new email address is discovered, and then those reverse relationships would populate the members record.
I initially started to do the answer where the action would actually populate the data in the master members record but then I realized it would be much simpler to get those fields created and to build all those actions if we just use a reverse look up to get the look up feels up to the master record.
Then all the action needs to do is to create for the master member record and populate a single email address.
