What should a developer's first step be when troubleshooting whether a DataRaptor Extract is retrieving data?
Suggested Answer: B
Get Premium Plat-Dev-210 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The PREVIEW tab in OmniScript allows the developer to test the DataRaptor Extract by providing a record ID and viewing the output data. This is a quick and easy way to troubleshoot whether the DataRaptor Extract is retrieving data correctly.
25 comments · newest first
LE
Lettie
6 months ago
D is useful for testing specific data, but I’d start with B for a broader view.
EL
Elfrieda
6 months ago
C seems logical too. Testing the card directly can help isolate the problem.
HA
Hannah
6 months ago
I prefer A. Reloading the page can show if the issue is with the console.
CH
Chandra
6 months ago
I think B is the best choice. Previewing in OmniScript gives immediate feedback.
VA
Valentine
6 months ago
Not sure if deactivating the card is really necessary.
JI
Jimmie
7 months ago
Adding a key/value pair is a solid move for testing.
SH
Shawnda
7 months ago
Surprised no one mentioned checking the DataRaptor logs first!
BU
Bulah
7 months ago
I think reloading the page is a waste of time.
ME
Melodie
7 months ago
Definitely start with the PREVIEW tab in OmniScript.
AL
Alayna
7 months ago
I heard the PREVIEW tab is the secret sauce for troubleshooting DataRaptors.
GL
Glory
8 months ago
Reload the page in the Lightning Console? Ain't nobody got time for that!
KE
Kerry
8 months ago
Adding a key/value pair to test the DataRaptor? Sounds like a waste of time.
RE
Remedios
8 months ago
Deactivating the card and layout? That's just asking for trouble.
KR
Kristal
8 months ago
The PREVIEW tab in OmniScript is the way to go!
GA
Gayla
9 months ago
Adding a key/value pair sounds like a valid troubleshooting step, but I wonder if it’s really the first thing to do in this scenario.
EL
Elin
9 months ago
I feel like deactivating the card and layout could be a bit extreme for just checking the DataRaptor, but it might help isolate the issue.
MA
Marsha
9 months ago
I remember practicing a similar question, and I think testing in the Lightning Console might be a good option too, but it feels a bit indirect.
KE
Keva
9 months ago
I think the first step should be to check the PREVIEW tab in OmniScript, but I'm not entirely sure if that's the best approach.
MA
Marla
9 months ago
Adding a key/value pair in the DataRaptor to test it sounds like a good troubleshooting step. I'll make sure to try that if the other options don't work.
CH
Chuck
10 months ago
I'd probably deactivate the card and layout, then go to the PREVIEW tab for the card to test the DataRaptor. That way I can isolate any issues with the Extract.
PA
Patria
10 months ago
Hmm, I'm a little unsure here. Should I try reloading the Lightning Console page first to see if that surfaces any issues?
LE
Leslie
10 months ago
I think I'd start by going to the PREVIEW tab in OmniScript to test the DataRaptor Extract. That seems like the most direct way to check if it's retrieving data.
BE
Bea
4 months ago
I usually check the Lightning Console first, but PREVIEW makes sense too.
GA
Gabriele
5 months ago
Definitely, it gives you a clear view of the data.
WI
Willard
6 months ago
I agree, the PREVIEW tab is the best first step.