Use Hash DPL Data in Scenario Editor Tests

Last reviewed: September 30, 2026

Use this article when a Scenario Editor test needs key-value style test data supplied through a Hash DPL.

What changed in this article

• Replaced terse Hash DPL wording with Scenario Editor-focused data guidance.
• Clarified when a Hash DPL is appropriate: lookup tables, keyed records, expected values, and reusable test configuration.
• Added validation checks for key uniqueness, missing keys, data refresh, sensitive values, and deterministic replay.

Validation workflow

1. Define the key field and confirm every required test case has a matching value.
2. Reference the Hash DPL from the Scenario Editor test and validate both a matching-key and a missing-key case.
3. Keep sensitive values out of plain test data or mask them before logging results.

Review note: This update keeps Hash DPL guidance practical without turning it into a generic data-storage page.

Last updated: September 30, 2026

If you have feedback on this topic, contact documentation@appvance.ai.