Melt Variable Functionality in Old Runtime with 7.X system
[dependent variable] [dummy variable] [MELT] [prequery] [template] [undefined variable] [variable] [variant]
Symptom
When running a template with the Old Runtime (ie. 3.X frontend) and the 7.X system (backend), the system will always melt the variable inspite of different values for the same variable.
Other terms
MELT, variant, prequery, template
Reason and Prerequisites
In the 7.X system, we will always melt the common variables into a single instance in the variable screen. This melting will be performed irrespective of any version of the frontend or any difference in the values of the variables.
Example:
A template is created with 3 Data providers as follows
DP1, Query A with variant “X”, variable value “M1″
DP2, Query B with variant “X”, variable value “M2″
DP3, Query B with variant “X”, variable value “M3″
Please note that the all the queries have the same variant name ie. X in our case, with different values for the variables.
In 7.X system, all the variables are melted into a single instance and that instance will hold the value of the 1st Data provider ie. M1 of the Data Provider DP1.
The reason for this behavior is the new java Web runtime where we cannot explicitly pass the variant value in the URL.
Solution
The only way to overcome this behavior is not to use the melt functionality ie. disable the MELT_VARIABLE parameter in the Web Application Designer.