Which configuration demonstrates wrapping a JSON object into a list for a DATARaptor Transform?

Which configuration demonstrates wrapping a JSON object into a list for a DATARaptor Transform?

• A. Set the Input JSON Path as List(Contact) and OutputJSON Path as Contact.
• B. Use a formula LIST(Contact), and add the output of the formula as the input in the Transform tab.
• C. Set the Input JSON Path as Contact and the Output JSON Path as List
• D. Set the Input JSON Path as Contact and Output JSON Path as List (Contact)

Answer: (B)

Wrapping a single JSON object into a list in a DataRaptor Transform is done by converting the object into a one-element collection before the Transform runs. The LIST() function creates exactly that: it takes the object (for example, Contact) and returns a list containing that object. Using a formula that produces LIST(Contact) and feeding that result as the input to the Transform makes the input data a list right from the start, which is what you need when the Transform is designed to work with arrays. This approach is preferred because it transforms the input shape into a collection without trying to treat a path as a list or altering the output path to force a list. The other configurations either reference list-like paths incorrectly or attempt to wrap at the output stage, which doesn’t achieve the desired input-to-list wrapping for the Transform. Using a formula to create LIST(Contact) and using that as the Transform input cleanly wraps the object into a list for subsequent processing.

Wrapping a single JSON object into a list in a DataRaptor Transform is done by converting the object into a one-element collection before the Transform runs. The LIST() function creates exactly that: it takes the object (for example, Contact) and returns a list containing that object. Using a formula that produces LIST(Contact) and feeding that result as the input to the Transform makes the input data a list right from the start, which is what you need when the Transform is designed to work with arrays.

This approach is preferred because it transforms the input shape into a collection without trying to treat a path as a list or altering the output path to force a list. The other configurations either reference list-like paths incorrectly or attempt to wrap at the output stage, which doesn’t achieve the desired input-to-list wrapping for the Transform. Using a formula to create LIST(Contact) and using that as the Transform input cleanly wraps the object into a list for subsequent processing.