SR11 change in Expression Editor syntax check

rwunderlich — Mon, 25 May 2015 16:50:15 GMT

We know that sometimes the expression editor syntax checker displays red squiggle lines in an expression that does not have a true error. It may be caused by an error in the syntax checker itself or the use of variables where the syntax checker may not be expected to understand. For example:

=FirstSortedValue(DISTINCT, Price, Date)

DISTINCT will be flagged even though DISTINCT is documented as being valid.

=Sum ({<$(s.ClearSubmitter),Function={If}>}#FunctionCount)

The comma will be flagged even though there will be a valid expression after variable substitution.

In SR10 and prior the edit status message in the upper left corner will be "Expression OK". So we can know the error is with the syntax checker, not the actual expression.

In SR11, the status message has changed. If there is any red squiggle, the status message now reads "Errors in expression". This means I can no longer say "ignore the squiggle if it says 'Expression OK'".

So where's the bug now, the squiggles or the "Errors in Expression" message?

Re: SR11 change in Expression Editor syntax check

jepeerik — Thu, 04 Jun 2015 08:48:14 GMT

Hi Rob,

Unfortunately this is true and I don't know why QlikView can't understand its own syntax.

But the improvement I saw was with the use of the -= in Set Analysis. This syntax is now correctly recognized by the Syntax checker and has no red squiggles anymore.

topic SR11 change in Expression Editor syntax check in QlikView

SR11 change in Expression Editor syntax check

Re: SR11 change in Expression Editor syntax check