During testing of a FlexCard, most fields render correctly but one field only shows the label. Which is the most likely cause?

During testing of a FlexCard, most fields render correctly but one field only shows the label. Which is the most likely cause?

• A. The fields have exceeded the maximum number allowed on the card.
• B. The data source key is invalid.
• C. There is a mismatch in the Data Source Input Map causing only the field to fail.
• D. The field is null in the Salesforce record.

Answer: (D)

FlexCard data binding shows a field’s label when the value from the data source is missing. In this setup, the label is static text that identifies the field, while the value area reflects the data resolved from the data source. If the Salesforce record’s field value is null, there is nothing to display in the value portion, so only the label remains visible. This behavior indicates the data binding exists but the underlying data is absent for that record. To confirm, check the actual value in Salesforce for that field on the specific record; if it’s null, the observed UI is expected. Other issues, like an invalid data source key or a mismatch in the Data Source Input Map, would typically disrupt the binding more broadly—often preventing the value from rendering at all or causing an error—rather than leaving only the value blank while the label stays.

FlexCard data binding shows a field’s label when the value from the data source is missing. In this setup, the label is static text that identifies the field, while the value area reflects the data resolved from the data source.

If the Salesforce record’s field value is null, there is nothing to display in the value portion, so only the label remains visible. This behavior indicates the data binding exists but the underlying data is absent for that record. To confirm, check the actual value in Salesforce for that field on the specific record; if it’s null, the observed UI is expected.

Other issues, like an invalid data source key or a mismatch in the Data Source Input Map, would typically disrupt the binding more broadly—often preventing the value from rendering at all or causing an error—rather than leaving only the value blank while the label stays.