QlikView Intermittent Concatenated Values During Reloads

The issue has some prerequisites as follows:

1. A larger number of CPU cores on the machine, unable to define an exact point but having more is more apt to cause the issue than less.
2. Concatenation of at least two fields into a key field in the load script.
3. Any of the following functions are in use in the load script
   • ASIN
   • ATAN
   • COS
   • COSH
   • EXP
   • FABS
   • LOG
   • LOG10
   • SIN
   • SINH
   • SQRT
   • SQR
   • TAN
   • TANH
   • SIGN
   • FACT

Environment: QlikView 11.20 SR16 and later SR's in the 11.20 track only.

The error only occurs when the evaluation is done in parallel, which depends on the entire load statement or hypercube. For text formatted results involving the affected functions, combined or spurious texts can also occur with, or without re-ordering.

May unpredictably result in the calculated expression values being arbitrarily re-ordered within the result. The re-ordering can be local to a limited range or affect the whole result-set.

Turning off the EnableParallelReload setting is one workaround, but this setting is global, so will impact all reload tasks and likely cause overall schedule time to increase due to single-threading.

Disable parallel reload by adding the following entry to the [Settings 7] section of the settings.ini file:

EnableParallelReload=0

Setting this value to 1 enables parallel reload.   Setting to 0 disables parallel reload.  By default this is enabled, so if there is no entry in the settings file then parallel reload is enabled.

Note the settings.ini file may be located in different areas and must be done on each machine running QlikView Desktop or QlikView Publisher Distribution Service.  
For Windows 10 and QlikView DESKTOP, the file would be located here: C:\Users\[USERNAME]\AppData\Roaming\QlikTech\QlikView
For Windows 10 and QlikView Publisher, the C:\Users\[QDS ACCOUNT NAME]\AppData\Roaming\QlikTech\QlikViewBatch

Currently there are no plans to 'fix' the issue in the 11.20 Releases impacted, to obtain fix you will need to upgrade to one of the newer supported tracks.