Which action helps map the RecordType DeveloperName when loading a Contact using DataRaptor Load?

Which action helps map the RecordType DeveloperName when loading a Contact using DataRaptor Load?

• A. Check the is Lookup property when mapping the fields
• B. Add a Link to RecordType object in the Contact Object with the id field
• C. Select RecordType in the Lookup object list. Development in the lookup Field list, and ID in the Lookup Requested Field list
• D. Select RecordType in the Lookup Object list. ID in the Lookup Field list, and Development in the Lookup requested Field list

Answer: (A)

Mapping a lookup relationship in DataRaptor Load lets you work with related records by their meaningful fields, not just by Id. For a Contact, RecordType is a lookup to the RecordType object, so marking the field as a lookup tells the loader to treat the incoming value as a reference to a related record. With this flag on, you can provide the RecordType’s DeveloperName in the load data and have the system resolve it to the correct RecordType, avoiding manual Id handling. The other options involve extra steps or configurations that aren’t needed to enable mapping by DeveloperName; simply enabling the lookup behavior is the correct approach.

Mapping a lookup relationship in DataRaptor Load lets you work with related records by their meaningful fields, not just by Id. For a Contact, RecordType is a lookup to the RecordType object, so marking the field as a lookup tells the loader to treat the incoming value as a reference to a related record. With this flag on, you can provide the RecordType’s DeveloperName in the load data and have the system resolve it to the correct RecordType, avoiding manual Id handling. The other options involve extra steps or configurations that aren’t needed to enable mapping by DeveloperName; simply enabling the lookup behavior is the correct approach.