|
| Re: report parameter as dataset filter works in dev, not on production [message #903623 is a reply to message #903584] |
Fri, 24 August 2012 15:06   |
|
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
>
>
>
|
|
|
|
|
|
|
| Re: report parameter as dataset filter works in dev, not on production [message #903673 is a reply to message #903653] |
Fri, 24 August 2012 20:15 |
|
Sam
Do you have any details on the production server?
Is is using the BIRT viewer? What is the url to run the report?
Jason
On 8/24/2012 1:30 PM, sam detweiler wrote:
> and the function we put in to control visibility of the headers also
> isn't working.
> on the production machine
>
> so I deployed the report design as a template
> then created a report from the template
> then ran the report (it prompted for project name)
>
> it reported the right stuff except
>
> 1. the filter didn't exclude records
> 2. the functions on the header rows didn't fire
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01952 seconds
] 
Search
Help
Register
Login
Home
