Store External Data Entries

The Store External Data Entries Advanced action stores several values at a time using the Data Exchange API. Theses values are referred to as “External Data” in the Runtime and Results tabs. A typical use is to grab business-related metrics through a Variable Extractor or through the SQL action and store them for later analysis. The entry values can be structured in a tree by specifying different paths in the path parameter.

• Information: If at least one of the variable values is not numerical, all values will be displayed in the URL column of the External Data.

Parameters

• variableName: The name of the multi-valued variable which contains the values to be stored. Example: “myValues” (not “${myValues}”).
• path: The string representing the list of nodes that contains the entry.
• unit (optional): The unit of the entry.
• code (optional): The string code of the status associated to the entry.
• message (optional): The message of the status associated to the entry.
• state (optional): The state of the status associated to the entry. Possible values are PASS and FAIL.
• DataExchangeAPIURL (optional): Where the DataExchange server is located. Optional, by default it is: http://${NL-ControllerIp}:7400/DataExchange/v1/Service.svc/.
• DataExchangeAPIKey: The identification key specified in NeoLoad.

Examples:

An example of values stored from a multi-valued variable:

• variableName: ids
• path: index|ids

A full example of values stored from a multi-valued variable:

• variableName: categories
• path: index|categories
• code: ERROR_INVALID_HANDLE
• message: The handle is invalid.
• state: FAIL
• DataExchangeAPIKey: myKey