Language parameter

[Georges Barakeh]

I'm writing a query and I would like to specify the language parameter.

I'm specifiying in the syntax the following:

 

language_code = @where:param:language@

It's returning an error in CA PPM 15.3 why?

 

Thanks,

[David Morton]

If you told us more information* we might be able to say "why".

 

* What error do you get?

 What is your (complete) NSQL?

that sort of thing.

 

(its very hard to help anyone when very little information is given )

[Georges Barakeh]

That's my sql statement for they query of the input control (report filtering parameter) and I want it to pick up the default CA PPM user language:

 

 

select a.id,
a.name,
a.sort_order
from cmn_lookups_v a
where a.lookup_type='IC_STAGE_LOOKUP'
and language_code='en'
and is_active=1;

 

 

********

I tried 

language_code=@where:param:language@

didn't work. I assume because this is SQL and not NSQL. what's the right syntax?

[Roland Parrotte]

The @WHERE:PARAM:LANGUAGE@ will only work in NSQL.

If you are running in an external product like TOAD or similar, then it won't know how to set this 'parameter' and you will need 'en' (assuming you want 'english').

[David Morton]

I don't recognise "query of the input control (report filtering parameter)" as being a usual place for NSQL (application querys or lookups).

 

But you need to fully describe what you are doing, what happens, what goes wrong - I have assumed you have a NSQL problem but it sounds like you are trying to use NSQL in a SQL context.

[Georges Barakeh]

I am on CA PPM 15.3.0.200.

in advanced reporting, I created a new report. This report requires some input paramters. I'm using a dynamic query to retrieve a list of values for these parameters. These values are translated. I would like to display these values based on the user language setting.

 

I found the solution.

The right syntax is:

language_code=$P{LoggedInUserAttribute_ppmUserLanguage}

This parameter picks up the user language value.

[David Morton]

Right, so the "problem" was that you were trying to use a NSQL built-in in Jaspersoft! 

 

Good that you have found the right Jaspersoft answer then.