Read and Write CSV Rows for Scenario Editor Data

Read and Write CSV Rows for Scenario Editor Data

Use CSV files as controlled test data sources when Scenario Editor tests need repeatable rows of input or expected values.

Recommended guidance

• Keep CSV headers clear and stable.
• Document whether rows are consumed once, reused, or reset between runs.
• Avoid writing sensitive runtime data to shared CSV files.
• Prefer DPL-managed data behavior when available.

Validation workflow

1. Prepare a small CSV sample with known rows.
2. Map fields to Scenario Editor inputs and validations.
3. Run a validation execution and confirm row usage.
4. Review generated or updated rows before using the data in larger runs.

Last updated: September 20, 2026