TDM - Handling Parameters

TDM Task - Selecting Entities Based on Parameters

A TDM task enables you to select a subset of entities based on a predefined list of parameters. For example, copy ten business customers that belong to Billing Cycle 1 and that are located in NY.
The parameters that are available for the task are attached to the LUs of the task's Business Entity. Parameters are defined at an LU level.

TDM Parameter Tables

When synced, the LUIs create and update the Parameters table in the TDM database. A separate parameters table is created for each LU. The naming convention of the parameters tables is <LU Name>_params.

Parameter tables are used for the following:

• Getting the list of available parameters per task.
• Getting the number of matching entities for the selected parameters of the task.
• Creating the entity list for the task if the task's selection method is based on parameters.
• Creating the entity list for the task if a random selection of entities is used whereby the entities are randomly selected from the parameters table in the task's root LU.

TDM Parameters - Implementation Guidelines

1. Verify that the LU_PARAMS is attached to the LU Schema.

2. Edit the COMBO_MAX_COUNT shared Global imported from the TDM Library if needed. By default the Global is populated with 49 and is checked when creating a TDM task using a parameters selection method. If the number of possible values in the TDM Parameters tables is smaller or equal to the COMBO_MAX_COUNT value, the parameter is handled as a combo parameter and a list of all possible values for this parameter is displayed. If a value is not selected from the list, the parameter has more values than the threshold defined in COMBO_MAX_COUNT and you must enter the value in the parameter.

   Add Parameters to the Logical Unit

3. Deploy the LU to the Fabric debug server.

4. Copy the trnLuParams translation object from the TDM_LIBRARY LU to the LU.

5. Edit the trnLuParams translation object (duplicated from the TDM_LIBRARY LU). Populate the parameter name and the SQL query of each parameter. The SQL query runs on the LU and must return only one column that is populated into the Parameter column of the LU_PARAMS table. To validate an SQL query, click the SQL button on the record to open the Query Builder where you can populate the Fabric DB connection and select the LU. For example:

   

6. Edit the LU_PARAMS table. Each parameter defined for the trnLuParams must be added to the LU table as a separate column. Set the type of all columns to Text. For example:

   

7. The LU population flow runs the fnEnrichmentLuParams function. This function runs the SQL queries of the trnLuParams and populates each column in the LU_PARAMS with the results of its related SQL query. Each parameter's column holds a JSON file that contains the values of the parameter. Each parameter can hold several values that are separated by a comma. For example:

   

   6. The fnEnrichmentLuParams function also creates and populates the <LU Name>_params table in the TDM DB.

Notes:

• The fnEnrichmentLuParams function runs the SQL queries to retrieve the LU tables' data. Therefore it has an execution order 999 to run after the remaining LU tables' population.
• The COLUMN_NAME value of the trnLuParams must be identical to the column_name added to LU_PARAMS table.
• The COLUMN_NAME value is displayed in the TDM Portal when the user selects parameters for a task.
• Do not include spaces or special characters in parameter names.
• Even if parameters do not need to be defined for an LU, the LU_PARAMS table with the ENTITY_ID and SOURCE_ENVIRONMENT columns must be added to the LU Schema to create the <LU Name>_params table in the TDM DB. The <LU Name>_params table is needed by both entities selection methods of a TDM task: Parameters and Random Selection.