Difference between revisions of "DES/Current/Designer/DataTable"
From Genesys Documentation
m (Ed.jamer@genesys.com moved page PEC-ROU/Current/Designer/DataTable to DES/Current/Designer/DataTable: Text replacement - "PEC-ROU/Current/Designer/" to "DES/Current/Designer/") |
(Published) |
||
Line 18: | Line 18: | ||
|structuredtext=Select a Data Table in the drop-down list. If you want to enable the option to use the data table as a variable, select '''Use variable'''. For example, you might select this option if you are using the same application in multiple locations, and each location needs to refer to a data table that is specific to that location. | |structuredtext=Select a Data Table in the drop-down list. If you want to enable the option to use the data table as a variable, select '''Use variable'''. For example, you might select this option if you are using the same application in multiple locations, and each location needs to refer to a data table that is specific to that location. | ||
− | Once you have selected a Data Table, you | + | Once you have selected a Data Table, you can configure the following: |
<ul> | <ul> | ||
<li>'''Look up by key(s)''' - For each key in your Data Table, enter a value (or variable, if '''Variable?''' is enabled) to use as an input for the '''Data Table''' block.</li> | <li>'''Look up by key(s)''' - For each key in your Data Table, enter a value (or variable, if '''Variable?''' is enabled) to use as an input for the '''Data Table''' block.</li> | ||
+ | <li>'''Strict comparisons''' - Select this option to use a stricter form of key matching when performing lookups. If enabled, Designer won't trim or ignore leading zeros in numeric columns or spaces in string columns. This option also prevents type-coercion during lookups; for example, strings won't be able to match numeric keys. | ||
+ | </li> | ||
<li>'''Multiple rows output''' - Select this option if the lookup key is of a date/time range data type, or if the data table contains multiple keys. | <li>'''Multiple rows output''' - Select this option if the lookup key is of a date/time range data type, or if the data table contains multiple keys. | ||
<li>'''Store loaded data into these variables''' - For each column in your Data Table, select a variable to hold the output value of your '''Data Table''' block.</li> | <li>'''Store loaded data into these variables''' - For each column in your Data Table, select a variable to hold the output value of your '''Data Table''' block.</li> | ||
</ul> | </ul> | ||
− | [[File: | + | [[File:des_data_table_properties_02.png]] |
|Status=No | |Status=No | ||
}}{{Section | }}{{Section |
Latest revision as of 17:14, November 19, 2021
Contents
Use this block when you want an application to reference one of your data tables.
Related documentation:
You can use the Data Tables block in any phase of your application to read values from a Data Table.
Data Table tab
Select a Data Table in the drop-down list. If you want to enable the option to use the data table as a variable, select Use variable. For example, you might select this option if you are using the same application in multiple locations, and each location needs to refer to a data table that is specific to that location.
Once you have selected a Data Table, you can configure the following:
- Look up by key(s) - For each key in your Data Table, enter a value (or variable, if Variable? is enabled) to use as an input for the Data Table block.
- Strict comparisons - Select this option to use a stricter form of key matching when performing lookups. If enabled, Designer won't trim or ignore leading zeros in numeric columns or spaces in string columns. This option also prevents type-coercion during lookups; for example, strings won't be able to match numeric keys.
- Multiple rows output - Select this option if the lookup key is of a date/time range data type, or if the data table contains multiple keys.
- Store loaded data into these variables - For each column in your Data Table, select a variable to hold the output value of your Data Table block.
Results tab
Comments or questions about this documentation? Contact us for support!