In principle, any extraction can be started by specifying its name.

In addition, there is also the possibility to use user-defined parameters in the extraction. The following screenshot shows a Where clause with two variables @PlantLow and @PlantHigh.

Extraction-User-Variables

Now click on the Run button and confirm the message, that the changes would be saved. When you open the Run dialog basing on this Where clause, you can find the variables in the second tab, so you can assign to them the wished value. Please use the @ symbol to identify variables. Please note that DATE values must be provided in form of YYYYMMDD.

Run-Extraction-Custom-Defined-Parameters

Thus we have now the following URL to set the values:

http://localhost:8085/?name=plants&**PlantLow=1000&PlantHigh=9999**

Replacing the variables with the data is logged and can be seen in the extraction log. To do this, click on the button Log in the Xtract Universal Designer:

User-Variables-In-Log

SQL Parameters for Database Destinations

In Xtract Universal user defined variables (custom parameters) that can be set as query string in the url, can be used as SQL parameter in the SQL statements for database destinations.

The following table extraktion has a custom parameter WNAME in the WHERE clause.

xu-customerparam-where

The extraction uses an Oracle destination. In the preparation statement the custom parameter can be used:

xu-customerparam-destination

Make sure to avoid name conflicts. The custom parameter in our example may not be called NAME1, since in the row processing statement we have the SQL parameter NAME1.