# Manage Multiple DPL Data Sources in Scenario Editor

# Manage Multiple DPL Data Sources in Scenario Editor

Use multiple DPL data sources only when a scenario needs clearly separated data sets, such as users, accounts, products, or generated values.

## Recommended guidance

- Name each DPL according to the business data it provides.
- Keep credentials and environment values out of DPL files and documentation.
- Document how rows advance, reset, or relate across data sources.
- Use the smallest data set that validates the test objective.

## Validation workflow

1. Identify each data source required by the scenario.
2. Map DPL fields to Scenario Editor inputs or validations.
3. Run a small validation execution to confirm row consumption behavior.
4. Review output before scaling or scheduling the suite.

**Last updated:** September 20, 2026