Value Tables

Updated on 03 Jul 2024
2 Minutes to read

Dark
Light

Article summary

Did you find this summary helpful?

Thank you for your feedback

General

Values tables are internal tables that Mail & Deploy stores that hold values from Datasource fields.

Example: Let's suppose you have a Report Parameter and you specify a Hub Input Field Specification for that parameter; you configured everything in such a way that the user can use a drop-down field to select a value for that parameter. Sometimes you may want to provide the user with a list of some or all values of a Datasource field. In such a scenario it wouldn't get good if Mail & Deploy would always read the current values of that particular datasource field whenever a user requests a report, because that would require to connect to the datasource (which may take a while) everytime a user opens the UI to request a report. Instead, you can use a value table that you can fill with the values of a particular datasource field (and automatically refresh it using a Reload Value Table Action on a regular basis) and let the user select a value from that value table.

Managing Value Tables

Value tables can be managed by logging on to the Management Service and clicking Value Tables in the menu. A value table may immediately be refreshed by clicking the  button; you can also schedule automatic reloads of values tables using Reload Value Table Actions in a Task.

Properties

Every value table has the following properties:

Name	Description
Name	The name of the value table.
Datasource	The Datasource to which the field from which to populate the value table belongs.
User Matching Mode	None. The value table does not contain user-specific values. Custom Username. The value table contains user-specific values and Users are matched using their custom username. Windows Account Name. The value table contains user-specific values and Users are matched using their windows account name. Custom Username or Windows Account Name. The value table contains user-specific values and Users are matched using their custom username or windows account name. Match Code. The value table contains user-specific values and Users are matched using their Match Code. E-Mail Address. The value table contains user-specific values and Users are matched using their E-Mail. More information can be found below.
User Field Name	The Datasource](/release35/docs/introduction-2) field that contains the user match. This property is only applicable if User Matching Mode is something other than None. See below for more information.
Value Field Name	The name of the Datasource Field from which to populate the value table.

User Specific Value Tables

If you select a User Matching Mode other than None, you can fill the value table with user-specific values. In order to do that, the associated Datasource needs to have two associated fields; one that contains the user match (e.g. the windows account name of the User ) and another field that contains the value to be loaded into the value table.

Example

Let's suppose you have a Datasource that contains two fields UserMatch and CountryName and these two fields have the following relation:

UserMatch	CountryName
domain\david	Austria
domain\david	Germany
domain\alice	Austria

If you load such a value table where User Matching Mode is Windows Account Name, User Field Name is UserMatch and Value Field Name is set to CountryName and use it in a Hub Input Field Specification, the User with windows account domain\david will be able to select from Austria and Germany and the user with windows account domain\alice will only be able to select Austria.

Was this article helpful?

What's Next

Deployments

Table of contents