Hi @Miguel 

conditions are also possible in a information source.

You have to put the columns by drag and drop in the field “Filters”.

SQL statements are not possible there.

Hi @Link 

Many thanks, that makes sense.

Could you please let me know if you see anything wrong with my syntax for the condition/filter below?

UPPER('$PROJECT_ID$')

UPPER('$SUB_PROJECT_ID$')

At the moment this syntax is not working for me in the lobby where these parameters are passed to the lobby element linked to this info source

Miguel

Hi @Miguel 

i think this approach won’t work. Because the column “Value” expect a value from data base.

Did you test it? Click on the button “Preview” on the same screen to test it.

Hi @Link 

Thank you, yes I tested and it does not return any values.

I would be surprise if there is no way to pass parameters from the Lobby header to a Lobby Element that uses a Data Source type Info Source. Surely this is possible somehow.

I think your suggestion is a good one, and I think the syntax is just not right. I don’t get an error message so I don’t think we are barking to the wrong tree ;-)

Miguel

Hi @Miguel 

to be hones I wouldn’t be suprised if there isn’t way to pass it. :-)

You don’t get an error message? Even if you type a value for the parameter?

@Link 

if I type values for the parameter, keeping the filters, I just get an empty table, please see screenshot.

So no error message

Miguel

@Link , I have solved this, as I was guessing it was the syntax at the filter level. The syntax below has worked like a gem ;-)

$PROJECT_ID$

$SUB_PROJECT_ID$

And what happen if you type the values directly in the column “Value”?

Does it show something?

@Link hardcoding values in the column value is standard functionality and yes that works, but been able to pass a parameter is more interesting. As I said changing the syntaxes of the parameterised value has worked for me. Many thanks for your initial input.