What is the Fields View?

A sortable, filterable table of every field WPLoadTester captured during recording. Each row shows the field name, type (URL query parameter, header, form field, JSON body, etc.), assigned data source if any, recorded value, and the transaction it came from. Filter by field type or text, mass-select related fields, edit many at once. The Fields View is how you parameterize without clicking through every page of a recorded scenario.

What data sources are supported?

Datasets (CSV, TSV, fixed-width files, or JDBC queries against SQL Server, Oracle, MySQL, Postgres, others). Sequence generators (ranges, randoms, dates, UUIDs, per-VU counters). Values extracted from prior responses (correlation, what ASM does automatically). Cookies. Inline value lists. Any source can be concatenated with any other before substitution.

Can I encode or transform data before substituting it?

Yes. URL encoding, form encoding, Base64, Base16. Transforms include MD5 / SHA digests and byte-length measurement. WPLoadTester applies the common encodings automatically based on field context; override or stack additional encodings explicitly when needed.

Field Parameterization · WPLoadTester 7

One recording. Thousands of distinct virtual users.

Q: How do I bind a field to a dataset?

Open the field (Fields View row or click in the recorded page), pick a data source in the Field Editor dialog: a column from a dataset, a sequence generator, a value extracted from a prior response, a cookie, or a concatenation of any of these. The binding persists; each virtual user pulls its own value at replay time.

The Fields View lists every field WPLoadTester captured during recording. Bind any of them to a dataset column, a sequence generator, a value extracted from a prior response, or a cookie. Each virtual user pulls its own row of values at replay time.

Request 7.0 Beta See Pricing

WPLoadTester Fields View. Table columns: Name, Type, Datasource, Recorded Value, Transaction Title. Rows show recorded fields including POST message body and URL query parameters (crc, flavor, svrid, type, vi), each with their type, recorded value, and source transaction. — The Fields View. Every captured field in one table, ready to bind to a data source.

The Fields View.

Open a recorded test case and the Fields View shows every field WPLoadTester captured: URL query parameters, form fields, hidden form fields, request headers, body fields (JSON, XML, form-encoded), cookies. One sortable, filterable, mass-editable table.

Filter by field type and text, both globally and per-column
Quick Search finds fields by name, value, or any column, including regex
Color coding distinguishes user-configured, auto-configured (by ASM), and unconfigured fields at a glance
Multi-select for mass-editing related fields in one operation
Saved configurations remember your column order, filters, and sorts. Pre-defined views ship for common tasks like changing hostnames, locating file uploads, or viewing recently changed fields

The Field Editor.

Pick a field, the Field Editor dialog opens. You bind that field to a data source: a column from a dataset, a sequence generator, a value extracted from a prior response (correlation), a cookie, or a concatenation of any of these. The binding persists in the test case; every virtual user pulls its own value at replay.

Whole-field or partial-field binding: you can replace an entire ?user=alice&flow=signup query string at once, or just the alice portion of one parameter. Mass-edit lets you bind a set of related fields together (every user_id across 40 transactions, for example) in one operation.

Encodings and transforms apply between the data source and the substituted value. URL encoding, form encoding, Base64, Base16; MD5 / SHA digests; byte-length measurement. WPLoadTester picks the encoding automatically based on field context, and you can override or stack additional encodings explicitly when the application needs them.

The data sources.

Five categories cover most parameterization needs. Mix and match per field.

Datasets.

A table of values external to the test case. WPLoadTester reads from CSV, TSV, and fixed-width files, or executes a JDBC query against SQL Server, Oracle, MySQL, Postgres, and other JDBC-compatible databases. Each row of the dataset binds to one virtual user (per-VU mode) or every VU draws from a shared pool (shared mode).

Sequence generators.

Generators for value patterns: ranges (sequential integers, dates), randoms, UUIDs, per-VU counters, current timestamps. Useful when you don’t want to maintain a CSV for values that follow a rule.

Values from prior responses.

The correlation primitive: extract a value from one response (a JSON field, an HTML hidden input, a header) and substitute it into a later request. ASM and the AI Assistant configure this automatically for the well-known dynamic-value patterns; explicit response-variable bindings handle the rest. Read about Automatic Configuration

Cookies.

The full cookie jar from the recorded session. Cookies set by responses propagate automatically to subsequent requests; explicit cookie bindings let you override or substitute values per virtual user.

Inline value lists.

Hard-coded value lists for small data sets where a file is overkill. Common for binary flags, environment names, or short enumerated choices.

Try field parameterization on your own test case.

Fields View, Field Editor, datasets, and sequence generators ship with every edition of WPLoadTester 7. Request the beta to run a parameterized cloud-scale test, or download the free single-machine edition to evaluate locally.