Test an Integration Procedure or Data Mapper

Read a debug run of a designer Preview on its Debug tab, get one without the designer, run it again with other input, send a test call of your own, or copy a call as Apex.

You want to see what an Integration Procedure or a Data Mapper does with some input, and then try the same call again with the input changed. The panel can show a debug run of a designer Preview step by step, send a call you compose, or hand you an Apex snippet.

Read a debug run on its Debug tab

1. Open the Integration Procedure or Data Mapper (DataRaptor) designer in the page you are inspecting, with DevTools open and Recording on in the Calls tab.
2. Press Execute on the designer's Preview. The run is listed in Calls as a call of its own, a debug run.
3. Click it. It opens on a Debug tab, first in the strip: the outcome, the time, the steps in run order with a bar for each step's share of the slowest, the response, the original input and the debug log. See Debug tab.
4. Click a step's number to open its input, options and output in place. Use the View picker to look at the Response, the Original input or the Debug log alone.

Run it again with other input

Sending a call is the only thing the panel does besides reading, so it is off until you allow it.

1. Open Settings (the gear, or press ,), find Sending and tick Allow test calls. Press I understand the first time. It is off again at every DevTools start. See Test calls.
2. Select the call and press Re-run…. The form opens with that call's input and options. For a designer Preview, keep the designer's own page open in the inspected tab, because the call needs its context.
3. Edit the input. Send waits until the JSON is valid. Format tidies it. From the data… opens a picker of the nodes of the script's current data: tick the ones the procedure reads, give each the key it expects in the as field (a dotted name such as Context.Account nests it), then press Add to input.
4. Press Send (Ctrl+Enter). The new call is listed with a test tag, and the answer opens on the row. See Re-run.

An Integration Procedure or a Data Mapper Load can create or change records in your org. Nothing is sent until you press Send.

Debug without the designer

An Integration Procedure asked for a debug run answers with the same run as the designer's Preview.

1. With Allow test calls on, select an Integration Procedure call the page made (Aura or LWR: a REST call carries no options).
2. Press Re-run… and add "isDebug": true to the Options.
3. Press Send. The answer, named after the procedure, opens on its Debug tab. See Debug tab.

The answer is bigger and slower, and the call still runs for real.

Start from nothing

1. With Allow test calls on, open New test call… (the … menu, or a toolbar button while Advanced is on).
2. Pick the kind, type the name, for example an Integration Procedure's Type_SubType key, and edit the input as above. It starts from the latest call of that kind.
3. Press Send.

Re-run as it was…, in the row menu, sends the call again unchanged, after asking.

Copy a call as Apex

1. Select an Integration Procedure or Data Mapper call.
2. Press Copy as Apex (the </> icon) in the detail head.
3. Paste it into the Developer Console's anonymous Apex window and run it there. Method signatures differ between versions, so treat the snippet as a starting point. See Copy as Apex.

Turn Mask values on first if the snippet is going into a ticket. Then compare the runs: Compare two runs.

Every control is described in the reference. More guides.