If you enable auto-enter options for import records, you can use a relationship that matches by both name fields to look up the ID during the import. But there are possible problems: names are not unique--the same name can match to more than one participant. And a name might not match to any participant.
So you might need to import into a staging table, resolve name matching issues and look up IDs before importing from your staging table into transactions.
I am trying this but not having any luck. I have participant table first name and last name related to transaction table first and last name. I have field options lookup values checked with starting table transactions, lookup from related table participant, copy value file ::ContactLastName etc...
I can't figure what I am missing. I have transaction and participant table relationships between ParticipantID (pk) ContactLastName and ContactFirstName
1 of 1 people found this helpful
The relationship used to look up IDs should only match by last name and first name fields. It should not include the ID field.
Your lookup would be set only on the ID field not the name fields as the name fields would already have data.
Keep in mind that you need two different sets of relationships between transactions and participants. One relationship is based on ID and should be used throughout your solution. The other is based on these name fields and should only be used to copy over the ID value so that your ID based relationship works. This will require creating two different occurrences of the same table in your relationship graph.
Thank you. I see what you are referring too. I appreciate your time and explanation.