---
title: "Value Tables"
slug: "value-tables"
updated: 2026-05-04T12:39:41Z
published: 2026-05-04T12:39:41Z
canonical: "help.mail-and-deploy.com/value-tables"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.mail-and-deploy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Value Tables

### General

Values tables are internal tables that Mail & Deploy stores that hold values from [Datasource](/release34/docs/introduction-to-datasources) fields.

> Example: Let's suppose you have a [Report Parameter](/release34/docs/report-parameter) and you specify a [Hub Input Field Specification](/release34/docs/hub-input-field-specifications) 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](/release34/docs/introduction-to-datasources) 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](/release34/docs/reload-value-table) 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](/release34/docs/services) 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](/release34/docs/reload-value-table) in a [Task](/release34/docs/tasks).

### Properties

Every value table has the following properties:

| Name | Description |
| --- | --- |
| Name | The name of the value table. |
| Datasource | The [Datasource](/release34/docs/introduction-to-datasources) 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](/release34/docs/users) are matched using their custom username. Windows Account Name. The value table contains user-specific values and [Users](/release34/docs/users) are matched using their windows account name. Custom Username or Windows Account Name. The value table contains user-specific values and [Users](/release34/docs/users) are matched using their custom username or windows account name. More information can be found below. |
| User Field Name | The Datasource](/release34/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](/release34/docs/introduction-to-datasources) 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](/release34/docs/introduction-to-datasources) needs to have two associated fields; one that contains the user match (e.g. the windows account name of the [User](/release34/docs/users) ) and another field that contains the value to be loaded into the value table.

#### Example

Let's suppose you have a [Datasource](/release34/docs/introduction-to-datasources) 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](/release34/docs/hub-input-field-specifications), the [User](/release34/docs/users) 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*.