For a customer with a new Engagement Manager becoming the Primary Contact for the Account, what type of mapping does a DataRaptor Load use to create the new contact and then add it as the Primary Contact?

For a customer with a new Engagement Manager becoming the Primary Contact for the Account, what type of mapping does a DataRaptor Load use to create the new contact and then add it as the Primary Contact?

• A. Linked Mapping
• B. Lookup Mapping
• C. Relationship Query
• D. Lookup Key

Answer: (A)

Linked Mapping is used when you need to create a new related record and immediately establish the relationship with another record created in the same DataRaptor Load. Here, you’re creating a new Contact and then linking it as the Account’s Primary Contact in one operation by passing the new Contact’s ID into the account lookup field. This direct, in-one-go linking is exactly what Linked Mapping enables. Lookup Mapping would only map to an existing related record, not create and link a new one. Relationship Query is for fetching related data to drive mappings, not for creating and tying new records together. Lookup Key relies on locating an existing record via a key to populate a lookup, not on creating a new child and linking it to a parent in the same load.

Linked Mapping is used when you need to create a new related record and immediately establish the relationship with another record created in the same DataRaptor Load. Here, you’re creating a new Contact and then linking it as the Account’s Primary Contact in one operation by passing the new Contact’s ID into the account lookup field. This direct, in-one-go linking is exactly what Linked Mapping enables.

Lookup Mapping would only map to an existing related record, not create and link a new one. Relationship Query is for fetching related data to drive mappings, not for creating and tying new records together. Lookup Key relies on locating an existing record via a key to populate a lookup, not on creating a new child and linking it to a parent in the same load.