What could cause a field in a FlexCard to display only its label while other fields show data?

What could cause a field in a FlexCard to display only its label while other fields show data?

• A. The Field name in the FlexCard state does not match the DataRaptor Extract's Output JSON Path name.
• B. In the Setup Panel, {recordId} is misspelled in the Data Source Input Map.
• C. There are No Test Data Test Parameters configured.
• D. In the FlexCard state, the Field type for the field does not match the type in the Salesforce record.

Answer: (A)

The binding between the FlexCard field and the data source is what determines whether a value shows up. In a FlexCard, each field pulls its value from the DataRaptor Extract output using a specific Output JSON Path name. If the Field name in the FlexCard state doesn’t exactly match that Output JSON Path, the card can’t locate the value to display. The result is that the field renders only its label (which is static) while the actual data stays unreadable because the binding points to nothing. The fix is to align the FlexCard field binding with the exact Output JSON Path name produced by the DataRaptor Extract. Other scenarios would produce different symptoms: a misspelled recordId would likely prevent data retrieval entirely or cause an error; no test data parameters affect testing rather than the live binding; a type mismatch could cause data formatting issues but wouldn’t specifically explain a missing bound value while the label remains.

The binding between the FlexCard field and the data source is what determines whether a value shows up. In a FlexCard, each field pulls its value from the DataRaptor Extract output using a specific Output JSON Path name. If the Field name in the FlexCard state doesn’t exactly match that Output JSON Path, the card can’t locate the value to display. The result is that the field renders only its label (which is static) while the actual data stays unreadable because the binding points to nothing. The fix is to align the FlexCard field binding with the exact Output JSON Path name produced by the DataRaptor Extract.

Other scenarios would produce different symptoms: a misspelled recordId would likely prevent data retrieval entirely or cause an error; no test data parameters affect testing rather than the live binding; a type mismatch could cause data formatting issues but wouldn’t specifically explain a missing bound value while the label remains.