jsmorley wrote: ↑
April 5th, 2019, 11:45 pm
Not sure I follow that. This certainly does work as designed and intended...
I know it does. As I said, I can't remember for sure, but I might have tried to nest variables on that occasion too, and probably trying all kinds of solutions I ended up throwing a [&
there as well.
Anyway, the fact is that the URL option of a WebParser handles a couple of very similar things in terms of syntax:
Somewhere along the line, it probably gets "confused" and goes the wrong way (e.g. expecting [Measures] instead of [#NestedVariables]). The fact that WebParser doesn't have a very long history of supporting dynamic variables (compared to other measure types) may be a factor in the occurence of such issues. Also, the URL option probably likes everything (variables, measures) to be resolved before they get to be used in the option...