In a FlexCard preview, if the RecordId test data type is wrong, which setting is likely causing the issue?

In a FlexCard preview, if the RecordId test data type is wrong, which setting is likely causing the issue?

• A. The Data Node field for the FlexCard is empty.
• B. The RecordId in the Test Data Source settings is for the wrong record type.
• C. There is not Salesforce record for the FlexCard based on the RecordId in the layout's Test Data Source Settings.
• D. The Attribute haven't been configured to pass the data to the fields.

Answer: (B)

In OmniStudio, a FlexCard preview pulls data through a Test Data Source that uses a RecordId to fetch the related Salesforce record. The type of that RecordId must match the Salesforce object the card is designed to display. When the RecordId test data type is wrong, the data source can’t resolve a valid record of the expected object, so the card can’t populate its fields in the preview. The setting most likely causing the issue is the RecordId in the Test Data Source settings being for the wrong record type. Ensure the RecordId type corresponds to the correct SObject (for example, Account, Case, etc.) and that the ID value matches an existing record of that object. If the type is correct but the ID references a different object, you’ll still see missing data or empty fields. Other problems, such as an empty Data Node field, missing attribute mappings, or no corresponding Salesforce record for the given ID, would also disrupt the preview but point to different misconfigurations rather than the record type mismatch.

In OmniStudio, a FlexCard preview pulls data through a Test Data Source that uses a RecordId to fetch the related Salesforce record. The type of that RecordId must match the Salesforce object the card is designed to display. When the RecordId test data type is wrong, the data source can’t resolve a valid record of the expected object, so the card can’t populate its fields in the preview.

The setting most likely causing the issue is the RecordId in the Test Data Source settings being for the wrong record type. Ensure the RecordId type corresponds to the correct SObject (for example, Account, Case, etc.) and that the ID value matches an existing record of that object. If the type is correct but the ID references a different object, you’ll still see missing data or empty fields.

Other problems, such as an empty Data Node field, missing attribute mappings, or no corresponding Salesforce record for the given ID, would also disrupt the preview but point to different misconfigurations rather than the record type mismatch.