How to Associate Dynamic Data

This task describes how to work with test configurations in ALM that access dynamic data.

Defining dynamic data enables you to specify sets of parameter values for the test from an external Microsoft Excel file.

Tip: The same Microsoft Excel file can be used as a data resource for different tests.


This task is part of a higher-level task. For details, see How to Work with Test Configurations.

  1. Prerequisites

    To work with dynamic data for UFT automated tests, make sure that the Unified Functional Testing Add-in for Business Process Testing is installed on the client computer. The Unified Functional Testing Add-in for Business Process Testing available from the Application Lifecycle Management Add-ins page (Help > Add-ins).

  2. Create a data table in Microsoft Excel

    This data table contains rows of values which become parameter values for each iteration of your test configuration.

    1. Create a spreadsheet:

      • In Microsoft Excel.

      • If working with business process tests, in Unified Functional Testing, you can export configuration values to a Microsoft Excel file, and use this file for your data table. See the information about exporting test iteration values into an Excel document in the Unified Functional Testing User Guide.

    2. Put test-level parameters in the first sheet. The entire test runs once for each row listed in the first sheet.


    3. Business Process Testing users can use subsequent sheets in the Excel file to override the business component iterations defined in business process tests and flows, according to the following guidelines:

      • The next sheets (meaning, all sheets but the first) represent components and their parameters.

        Note: If a component does not contain parameters, the Excel does not contain a sheet for that component.

      • In each sheet, the column headings (first row) containing the parameter names must be in one of the following formats:


          This format is the general, default format.


          This format is useful for keeping sheet names short.


          This format is useful if the name of the sheet is the same as the name of the component, and you need to keep the sheet names short.


        • If the same component has been added to the same test multiple times, the numerical instance of the component in the test is listed between the component name and the parameter name. The component instances are listed according to their order in the test script, not necessarily in the order of the original numerical instance of the component when inserted.

        • The sheet name cannot be more than 32 characters long and cannot contain special characters. (This is a Microsoft Excel limitation.)

          Tip: When specifying column headings, it is helpful to use one of the last two formats listed above for parameter names in order to avoid this limitation.

      • Specify values for each parameter under the parameter names, each on a different row. Each row represents an iteration. Add iterations as necessary.


      The first sheet, that corresponds to the OrderingBooks business process test. The test will run once, because it is designed to run only for one store, BooksOnline.

      The second sheet corresponds to the Login business component. This business component will iterate only once, because only one user is listed as logging in.

      The third sheet corresponds to the OrderBooks business component. This business component currently iterates only once, because only book is listed.

      If we want to iterate the component multiple times, we could modify the third sheet (that corresponds to the OrderBooks business component) so that it more rows are added. This business component will iterate for every book listed—in this case, six times.

    4. Save the file.

      • When editing the spreadsheet in Excel, if no values / iterations are specified for a particular parameter defined in the component, test, or flow, an exception will occur at run-time.

      • If a component, group, or flow has input parameters that reference the output parameters of a different business component or flow, differences between the number of iterations can result in an error. The parameter name in the Iterations dialog box is displayed in red, indicating an iteration range mismatch.