Editor-trouble with a set_expression

[datanibbler]

Hi,

I have the following issue - which is rather an issue of the editor (and thus a feature request or whatchamacallit), it works like it is.

=> My expression in this scenario (one of the most complex of this sort which I have) is:

COUNT({$<%Datum -= {"$(=DATE(v_today))"}>} DISTINCT Pers_Nr5)
-   SUM({$<%Datum = {"$(= '<' & DATE(v_today))"}>} Gestempelt)
-   SUM({$<dienstfrei={0}, Urlaub={0}>} Kennz_krank)
-   SUM({$<%Datum = {"$(= '<' & DATE(v_today))"}, dienstfrei={0}, Kennz_krank={0}>} Urlaub)
-   SUM({$<%Datum = {"$(= '<' & DATE(v_today))"}, Urlaub={0}, Kennz_krank={0}>} dienstfrei)

As I said, this works fine.

<=> The trouble is, the editor in QlikView does not seem to recognize that '-=' in the first line of the set_expression => everything from that point on is underlined in red, which makes it a bit difficult to detect syntax_errors after that, should there be any.

<=> Still, the editor says "Expression okay" 😉

Is there any chance of this bug in the editor being fixed?

Thanks a lot!

Best regards,

DataNibbler

[Nicole-Smith]

I can't answer about it being fixed, but you could use this syntax instead which won't show it as having syntax errors:

COUNT({$-<%Datum = {"$(=DATE(v_today))"}>} DISTINCT Pers_Nr5)

(I changed the $ to $- and the -= to just 😃

[jaimeaguilar]

Hi, there are some bugs in editor highlighting like these:

When you use -=, +=, *=, /=

this other one:

also using variables like this:

however, in most cases there are workarounds or alternative ways of getting to the same result, like what Nicole suggested,

regards

[rbecher]

I wouldn't use different syntax just to satisfy the editor's highlighting. This could end up in confusion about the initial intention of the set analysis.

[datanibbler]

Hi all,

I'm a bit torn on this one. I have chosen this specific syntax because, in a way, it is more elegant and, like Ralf said, I wouldn't like to change my style of doing things just to satisfy the editor's capabilities or incapabilities.

On the other hand, well, you have to accept some things if you cannot change them ...

Also, it would make it easier for anyone else to reconstruct the intention of that statement if it wasn't all underlined - which is one of my principal objectives in developing my apps.

Thanks for your ideas and comments!

I'll think about it.

Best regards,

DataNibbler

[jaimeaguilar]

I'm agree that contructing formulas wouldn't be based on satisfying syntax highlighting. However, I think that sometimes it can be confusing and difficult to debug a formula when syntax stops working correctly. I hope this issue gets fixed in next releases,

regards