Use Scenario-Wide DPL Data

Last reviewed: September 30, 2026

Use this article when a Scenario Editor test needs one DPL data source available across multiple steps or actions in the same scenario.

What changed in this article

• Normalized the title and explained scenario-wide DPL scope in current Scenario Editor terms.
• Added guidance for choosing scenario-wide DPLs versus step-specific data when values must be reused across the run.
• Added checks for row selection, iteration behavior, missing values, concurrency, and sensitive data handling.

Validation workflow

1. Choose scenario-wide DPL only when multiple steps need the same data context.
2. Validate row selection and iteration behavior with a small run before scaling.
3. Confirm logs and reports expose enough row context for debugging without exposing sensitive values.

Review note: This page now differentiates shared scenario data from one-off step data.

Last updated: September 30, 2026

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