A FlexCard displays data by binding its elements to the JSON data returned from its data source (e.g., a DataRaptor). Each field element uses a merge field, such as {FieldName}, to reference a specific key-value pair in the JSON. If the name used in the FlexCard element's merge field does not exactly match the corresponding key (JSON Path) in the output from the DataRaptor, the FlexCard cannot find the data to display. Consequently, only the field's label will be rendered, while other correctly mapped fields will show their data.

A. A misspelled {recordId} in the Data Source Input Map would cause the entire data source to fail, as it wouldn't receive the correct context. This would result in no data being displayed for any field.

C. A mismatch between the FlexCard field type and the Salesforce data type might cause formatting issues (e.g., a date appearing as a string), but it typically does not prevent the data from being rendered entirely.

D. Test Parameters are used only for previewing the FlexCard within the designer. Their absence or misconfiguration does not affect the FlexCard's behavior at runtime when it is activated and receives live data.

1. Salesforce OmniStudio Documentation

"Display Data on a FlexCard": This section details how to use merge fields to display data from a data source. It states

"To access a node

enter the node's name inside curly braces. For example

to access the Name node from a data source

enter {Name}." This highlights the direct name-matching requirement between the FlexCard element and the JSON data key.

2. Salesforce OmniStudio Documentation

"FlexCard Data Source Properties": This guide explains the role of the Input Map

including passing the recordId. It clarifies that this input is critical for the data source to fetch the correct record. An error here

as suggested in option A

would prevent the data source from returning any record-specific data.

3. Salesforce OmniStudio Documentation

"Preview a FlexCard with Test Parameters": This document explains that Test Parameters are used to "test your FlexCard's data source and layout" within the designer. This confirms that they are a design-time tool and their configuration does not impact the FlexCard's functionality in a live environment

making option D incorrect.