Hi,
I have been working with variables shared across BEx queries.
I have tested the following using DS 1.3 on BO 4.1 SP4.
I have two queries each using the same variable (PROMPT_EXAMPLE_ID) as a prompt.
What I discovered is that the variable container (VC) as Martin Kolb is blogging about, is working fine when using local mode.
When I use them on the BO platform (connecting to two different OLAP connections, one for each query) they work using the variable initialization (and actually also by using "on startup") without any issue with this logic:
APPLICATION.setVariableValue("PROMPT_EXAMPLE_ID","1");
But when I apply the same logic through an "onclick" event or an "onselect" event. In that case I receive the error attached to this discussion.
I did a bit more debugging and it turns out, that if I use the same OLAP connection, but then change the query used for one of the connections, it actually works. So it seems like there is a bug when the VC is merging across OLAP connections.
The question is, is it recommended to use one "dummy OLAP connection" for all data sources and then change from the default provided query to a different one? The changing of query for an OLAP connection is something that you can't do in e.g. Web Intelligence or Dashboards (Xcelsius), Design Studio is the first place I have come across that possibility.
Have anyone experience the same issue? - I have tested on three different platforms, with three different sets of queries. I am guessing it is a bug in the software, specifically related to the event triggering?