Which option uses a valid Extract JSON Path for a nested field from related objects when configuring a DataRaptor Extract Action?

Which option uses a valid Extract JSON Path for a nested field from related objects when configuring a DataRaptor Extract Action?

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

Answer: (B)

In a DataRaptor Extract Action, you pull values by following the data shape with a JSON Path that can traverse related records. To get a field from a related object, you navigate through the relationship from the primary object using dot notation. If you start from a Contact and want the Name on its related Account, the correct path is Contact.Account.Name. This directly reflects the nested relationship and retrieves the Name from the linked Account. The other options either reference a field on the primary object itself (Contact.Name), reference a root object that isn’t the starting point for this nested lookup (Account.Name), or add an extra, invalid segment (Contact.Account.Name.Name) that doesn’t correspond to a real field in the data structure.

In a DataRaptor Extract Action, you pull values by following the data shape with a JSON Path that can traverse related records. To get a field from a related object, you navigate through the relationship from the primary object using dot notation. If you start from a Contact and want the Name on its related Account, the correct path is Contact.Account.Name. This directly reflects the nested relationship and retrieves the Name from the linked Account.

The other options either reference a field on the primary object itself (Contact.Name), reference a root object that isn’t the starting point for this nested lookup (Account.Name), or add an extra, invalid segment (Contact.Account.Name.Name) that doesn’t correspond to a real field in the data structure.