Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

MapSubstring - script function

The MapSubstring script function is used to map parts of any expression to a previously loaded mapping table. The mapping is case sensitive and non-iterative, and substrings are mapped from left to right.

Syntax:  

MapSubstring('map_name', expression)

 

Return data type: string

Arguments:  

Arguments
Argument Description
map_name

The name of a mapping table previously read by a mapping load or a mapping select statement. The name must be enclosed by single straight quotation marks.

Warning noteIf you use this function in a macro expanded variable and refer to a mapping table that does not exist, the function call fails and a field is not created.
expression The expression whose result is to be mapped by substrings.

Example:  

In this example we load a list of product models. Each model has a set of attributes that are described by a composite code. Using the mapping table with MapSubstring, we can expand the attribute codes to a description.

map2: mapping LOAD * Inline [ AttCode, Attribute R, Red Y, Yellow B, Blue C, Cotton P, Polyester S, Small M, Medium L, Large ] ; Productmodels: LOAD *, MapSubString('map2', AttCode) as Description Inline [ Model, AttCode Twixie, R C S Boomer, B P L Raven, Y P M Seedling, R C L SeedlingPlus, R C L with hood Younger, B C with patch MultiStripe, R Y B C S/M/L ] ; // We don't need the AttCode anymore Drop Field 'AttCode';

 

The resulting table looks like this:

Resulting table
Model Description
Twixie Red Cotton Small
Boomer Blue Polyester Large
Raven Yellow Polyester Medium
Seedling Red Cotton Large
SeedlingPlus Red Cotton Large with hood
Younger Blue Cotton with patch
MultiStripe Red Yellow Blue Cotton Small/Medium/Large

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!