Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344854 - 'Report parameters' are not visible from 'Data Set - Property binding'
Summary: 'Report parameters' are not visible from 'Data Set - Property binding'
Status: CLOSED DUPLICATE of bug 340560
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7.0   Edit
Assignee: Birt-ReportDesigner CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-05 11:18 EDT by Michal Oškera CLA
Modified: 2011-05-26 13:32 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Oškera CLA 2011-05-05 11:18:36 EDT 
Build Identifier: Eclipse BuildID: 20110218-0911, BIRT: 2.6.2.r262_v20110209

It is not possible to reference report parameters in property binding in data set definition.

Although the JavaScript Formula editor offers existing report parameters for including them to the JS expression representing the Property binding, the attempt to save Data Set edited in this way fail saying: Error evaluating Javascript expression. Script engine error: Report parameter "tstParam" does not exist.

Similar experience is also described in this forum thread:
http://www.birt-exchange.org/org/forum/index.php/topic/21959-report-parameters-and-datasource-property-bindings/page__s__548798ab68c81adcd2505bc008e9c8e9


Reproducible: Always

Steps to Reproduce:
1. Create report parameter tstParam
2. Create data set tstDS
3. Write simple query into Query folder of edited tstDS
4. Rewrite query into Property binding extending it with tstParam (e.g. + params["tstParam"])
5. Click OK button
6. Exception appears saying that Report parameter tstParam does not exist.
Comment 1 Xiaoying Gu CLA 2011-05-06 03:30:56 EDT 

*** This bug has been marked as a duplicate of bug 340560 ***