Which JSON path correctly points to a Contact's Account Name when configuring a DataRaptor extract? If a Contact has a related Account, what is the proper path?

Which JSON path correctly points to a Contact's Account Name when configuring a DataRaptor extract? If a Contact has a related Account, what is the proper path?

• A. Contact.Name
• B. Contact.Account.Name
• C. Account.Name
• D. Contact.Account.Name.Name

Answer: (B)

In a DataRaptor extract, you access related records by chaining the relationship name with dot notation. To get the Account name linked to a Contact, you navigate through the Contact to its related Account, then to the Account’s Name: Contact.Account.Name. This is the only path that correctly targets the Account’s Name field starting from a Contact. The other options either pull the contact’s own name (Contact.Name), refer to an Account object without going through the Contact relationship (Account.Name), or add an extra, incorrect field (Contact.Account.Name.Name).

In a DataRaptor extract, you access related records by chaining the relationship name with dot notation. To get the Account name linked to a Contact, you navigate through the Contact to its related Account, then to the Account’s Name: Contact.Account.Name.

This is the only path that correctly targets the Account’s Name field starting from a Contact. The other options either pull the contact’s own name (Contact.Name), refer to an Account object without going through the Contact relationship (Account.Name), or add an extra, incorrect field (Contact.Account.Name.Name).