A developer has a requirement to create a child FlexCard that contain all of its parent FlexCard’s records in a Datatable.

To pass the entire dataset from a parent FlexCard to a child FlexCard, you must use the {Records} merge field syntax. When a parent FlexCard's data source (like a DataRaptor) returns a list of records, this data is typically stored in a JSON node named Records. By setting the records attribute of the child FlexCard element to {Records}, the entire array of records from the parent's data JSON is passed down. The child FlexCard's Datatable can then use this inherited data as its source, fulfilling the requirement to display all of the parent's records.

A. {Records[0]}: This syntax passes only the first record from the parent's list of records, not the entire list as required by the Datatable.

C. {Params.records}: This syntax is used to access data passed into the parent FlexCard from its container, such as URL parameters or Lightning page attributes, not for passing data between parent and child FlexCards.

D. {recordId}: This variable holds the ID of the record context where the FlexCard is placed. It represents a single ID, not a list of records from the parent's data source.

1. Salesforce OmniStudio Documentation

"Pass Data Between a Parent and a Child FlexCard": This official guide explicitly states the method for this scenario. It instructs: "To pass a list of records from a parent FlexCard to a child FlexCard

from the parent FlexCard

drag a child FlexCard into a state. In the Properties panel

in the Records field

enter {records}." This directly supports using the node containing the array of records.

2. Salesforce OmniStudio Documentation

"FlexCards Data JSON": This document explains the structure of data within a FlexCard. The output of a data source is mapped to a node in the data JSON. When a DataRaptor returns a list

it is common practice to name this node Records

which is then accessible via the {Records} merge field.

3. Salesforce OmniStudio Documentation

"FlexCard Data Source Properties": This section details how data sources populate the FlexCard. For a DataRaptor Extract that fetches multiple records

the "Result JSON Path" is often left as the default

which creates a top-level node (e.g.

Records) containing the array of results. This array is what needs to be passed to the child.