Selecting an lov parameter value sometimes not passed correctly

Question

When selecting a value from an LOV parameter, sometimes the parameter value doesn't seem to get passed correctly to the data template query.
For example, let's say I have the following LOV parameter called "risk":
Some Risk
New Risk
Other Risk
Last Risk
When I select "Some Risk", I would get correct results and when viewing the "Data" xml, I can see the parameter with the right value:
<RISK>Some Risk</RISK>
But when I select "New Risk" the results are incorrect and the xml shows:
<RISK />
as if the value was not passed as the bind parameter value for the dataset query.
Any idea what I'm doing wrong? Is this a BIP bug or is there a workaround?

Answer 1

Hi, thanks for the reply.
The LOV is of "SQL Query" type (not fixed data) and the values were retrieved from the database.
Supposing this was the sql query for my "risk" parameter LOV:
select dimvaltl.GENERIC_VAL_NAME
from GENERIC_VAL_TL dimvaltl,
GENERIC_TL dimtl
where dimtl.GENERIC_NAME = 'Risk'
and dimvaltl.GENERIC_ID = dimtl.GENERIC_ID
order by dimvaltl.GENERIC_VAL_NAME
And supposing this was the sql query in the data template dataset:
select pdimv.ID
from GENERIC_V pdimv
where pdimv.NAME = 'Risk'
and pdimv.VALUE in (:risk)))
If risk is empty, obviously the query would not work. I noticed the xml generated sometimes show the selected parameter value and sometimes don't, as if BIP is not passing it to the dataset query as bind parameter value.
Incidentally I have other lov parameters that works fine, the only difference I can think of is that for this LOV query I am doing a join instead of a simple select statement from one table.