Free Salesforce Plat-Dev-210 Actual Exam Questions s - Question 3 Discussion

Question No. 3
When launching an OmniScript from an action on a FlexCard, the OmniScript displays, but no
Salesforce data is populated:
Which two errors could cause this behavior?
Choose 2 answers
Choose 2 answers
Select all that apply, then reveal solution.
US
FQ
Farhan Q.
2026-02-21

B, D. If the DataRaptor Extract isn’t active, it won’t pull any data. Also, a typo in the Input Parameters filter would stop the correct record from being fetched, causing no data to show.

0
FQ
Farhan Q.
2026-02-18

It’s A and D because no Id or wrong filter means no data query.

0
NH
Noah H.
2026-02-17

C imo, if the OmniScript version isn’t active, it might still launch an old version that doesn’t pull data properly. Also, A fits since a blank Id stops record context from reaching the script.

0
NH
Noah H.
2026-02-12

A imo, the blank Id Field in the FlexCard action is a clear no-go for passing record context, so that definitely causes no data to load. D also fits because if the input parameter filter value is misspelled in the DataRaptor Extract, it won’t correctly pull data even if everything else is set right. B and C might cause issues, but since the OmniScript is showing up at least, it suggests those aren’t the root problems here. So A and D seem like the most direct reasons for no Salesforce data populating.

0
NH
Noah H.
2026-02-11

A D - Blank Id or wrong filter stops data from loading.

0
NH
Noah H.
2026-01-27

Good point on B. Even if the OmniScript launches, no data will show if the DataRaptor Extract isn’t active, so B makes sense. I’d go with A and B.

0
NH
Noah H.
2026-01-25

Option A makes sense because if the Id field on the FlexCard action is blank, the OmniScript won’t get the record context needed to fetch data. Also, option D fits since a misspelled Input Parameters Filter in the DataRaptor Extract would prevent it from retrieving the right data, causing no info to populate. B could be possible but seems less likely because the question implies the OmniScript runs but just doesn’t show data, so the DataRaptor probably exists but has an input issue rather than being inactive.

0
BS
Brian S.
2026-01-23

B imo, no active DataRaptor means no data; C less likely if OmniScript shows up.

0
RU
Rizwan U.
2026-01-17

It’s A and D for me. If the Id field on the FlexCard action is blank, the OmniScript won’t have a record context, so no data shows up. Plus, a misspelled Input Parameter in the DataRaptor Extract would prevent the right data from being fetched. The OmniScript showing up rules out C since it has to be active to display. B could cause issues, but if it was inactive, I think the OmniScript might not even run properly or would throw an error rather than just missing data.

0
RU
Rizwan U.
2026-01-15

Maybe A and D, since if the FlexCard action’s Id field is empty, the script won’t know what record to pull. And a misspelled filter value in DataRaptor would definitely stop data from loading.

0
RU
Rizwan U.
2026-01-15

Hmm, I’m not sure if the issue could be that the DataRaptor Extract isn’t active or maybe the Input Parameters are off. Could it be that both B and D cause no data to show up? Or does C play a part if the OmniScript itself isn’t active? Would love to know what setups people have seen run into this.

0