When a form collects more than one video, the important question is not whether both clips uploaded. It is whether each recorder field keeps its identity through the saved entry and the destination post. Test with visibly different recordings so a swapped mapping cannot pass unnoticed.
Establish the supported configuration
Pipe 1.6 adds multiple recorder fields per form and an existing-video upload option. Its changelog also identifies a recorded-video population fix involving Advanced Post Creation's Edit Post setting. Check installed versions and the current Pipe documentation before changing a production form. Do not assume every post-editing extension uses the same integration path.
This workflow tests identity and mapping. It does not establish access-control policy, media retention or permission to publish a person's recording. Set those requirements separately. Keep the test environment private and use synthetic clips containing no personal information.
Write the mapping contract before editing the form
Use two short clips with unmistakable markers: “introduction A” and “demonstration B.” Give the recorder fields different labels and record their actual field IDs. Record the intended post type, post ID when editing, and destination field or content location for each clip.
For example, recorder field 4 might supply an introduction and recorder field 9 might supply a demonstration. Those are illustrative IDs, not settings to paste into your form. A renamed label is not evidence that the underlying field ID changed. A duplicated or rebuilt field may have a new ID even if its label looks familiar.
| Source identity |
Saved entry check |
Intended destination |
| Recorder A and its real field ID |
Reference plays introduction A |
Introduction location |
| Recorder B and its real field ID |
Reference plays demonstration B |
Demonstration location |
| Existing post being edited |
Correct post ID and current markers |
No unrelated post changes |
Test creation before testing editing
Submit the simplest two-recording fixture once. Inspect the entry before checking the created post. If the entry already has swapped or missing references, a destination template change will not repair the source record. Compare the actual field values privately and keep signed media links out of public tickets.
If the entry is correct, inspect the post creation configuration and the resulting post. Trace each destination back to its configured source rather than relying on visual field order. A form layout change should not silently change the intended mapping contract. Verify any conditional feed rule that controls whether post creation runs at all.
Distinct markers connect each recorder field to its saved entry value and intended post destination. Explanatory diagram.
Exercise the edit path without replacing everything
Use a disposable staging post with known original recordings. Open it through the integration's supported edit workflow. Confirm both existing values populate in the intended fields before recording anything new. If one is missing, preserve that state and the installed versions before saving over the post.
Replace only the introduction. Leave the demonstration unchanged, submit once, and compare both destinations. Then repeat with only the demonstration changed. These asymmetric tests catch a mapping that looks correct when every field is replaced but loses an untouched value during an edit.
Finally test an intentionally blank optional recorder according to your documented business rule. Decide whether blank means preserve, remove or reject. Do not infer this behavior from a label. If the integration cannot express the desired rule safely, stop and obtain a supported implementation rather than patching serialized values directly in the database.
Include failure and retry coverage
Trigger one unrelated validation error and confirm both recorder identities survive the correction. The Pipe validation and completion guide covers that boundary. If existing-file upload is enabled, test it separately from a fresh recording and verify the destination marker again. Identical-looking thumbnails are not a sufficient acceptance test.
Record the form ID, entry ID, destination post ID, recorder field IDs and test outcome in a private handoff. A reliable result shows correct creation, correct initial population when editing, and preservation of the untouched recording during a one-field replacement. It also leaves unrelated posts unchanged.
Use field-level validation logging when the submission fails before a destination is created. HandL WP can investigate the integration with the sanitized mapping contract and a reproducible staging fixture. There is no need to expose real interview recordings to explain a field identity problem.
Sources reviewed November 2, 2026. Examples and diagrams are diagnostic aids, not customer test results.