report parameter as dataset filter works in dev, not on production [message #903584] |
Fri, 24 August 2012 08:24  |
Eclipse User |
|
|
|
so I successfully created my nested table, (Thanks Jason), and migrated it to the production system (Birt 3.2.21)
my leaf most dataset uses a defined filter (its second filter) which uses the report parameter.
in the designer testing it work perfectly..
in the production system this parameter appears to be ignored.
the Birt version shipped with IBM Ration Team Concert is unknown to me,
but the product shipped last October, and the major version was released June 2011,
over year ago..
(so this could be a bug or lack of feature in the runtime)
is there another way, short of passing the parm thru the nested tables as a calculated field? (this wouldn't be hard, just time consuming)
Thanks
Sam
|
|
|
Re: report parameter as dataset filter works in dev, not on production [message #903623 is a reply to message #903584] |
Fri, 24 August 2012 11:06   |
Eclipse User |
|
|
|
Sam
Can you put that file io im I sent you in the filter to see what the
parameter value is when the filter is calculated?
Jason
On 8/24/2012 8:24 AM, sam detewiler wrote:
> so I successfully created my nested table, (Thanks Jason), and migrated
> it to the production system (Birt 3.2.21)
>
> my leaf most dataset uses a defined filter (its second filter) which
> uses the report parameter.
> in the designer testing it work perfectly.. in the production system
> this parameter appears to be ignored. the Birt version shipped with IBM
> Ration Team Concert is unknown to me,
> but the product shipped last October, and the major version was released
> June 2011,
> over year ago..
> (so this could be a bug or lack of feature in the runtime)
>
> is there another way, short of passing the parm thru the nested tables
> as a calculated field? (this wouldn't be hard, just time consuming)
>
> Thanks
>
> Sam
>
>
>
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04895 seconds