WHAT IS A VALUE TABLE?
In a Mapping Table, you can translate values by providing a match dimension value including its translated version. Sometimes it can be helpful to have a predefined selection of values to translate to in a drop-down list instead of manually entering the value. This prevents spelling errors and makes manually populating mapping tables much faster and less error-prone.
A value table stores these predefined values. The most common usage of a value table is the predefined selection of Explore Workspaces. However, you can also create a value table for any other type of value, either by creating a static value table or by dynamically tracking all available values within a certain Datastream column .
This can be helpful when you want to translate multiple values from a certain column to a unified value in a mapping table.
EXAMPLE
You are collecting data from multiple sources, across which there are multiple names for the same product. You can use a mapping table to standardize these names. Instead of typing the complete standardized name for each mapping table entry, you can simply select the universal title from the drop-down list. The value table is the source for these standardized titles.
CREATING A VALUE TABLE
- Navigate to "Enrich".
- Go to Value Tables and Click "Add+".
- Populate "Workspace" and "Name", leave "Sync Provider" blank.
- a. Click "Add another Value Table Entry" and insert the value that you'd like to be available in the mapping table's drop-down list.
b. Alternatively, if you save a blank Value Table, the "Import from CSV" button will appear, allowing you to select a file that contains 1 column with the values you'd like to have available in the drop-down list. - Save the value table once you have added all required entries.
POPULATING A MAPPING TABLE USING VALUE TABLE
- Go to the mapping table and select the created Value Table under "Default Value Table".
- When populating the mapping table click on the link icon
of the right column to open the list of available values.
Comments
0 comments
Article is closed for comments.