Bugzilla – Full Text Bug Listing
| Summary: | [2.3.2][Automation]The joint result of script computed column is incorrect | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | mindan xu <mindan.xu> | ||||
| Component: | BIRT | Assignee: | Zhang Lei <LZhang> | ||||
| Status: | VERIFIED INVALID | QA Contact: | Xiaoying Gu <bluesoldier> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | bluesoldier, mwu | ||||
| Version: | 2.2.2 | ||||||
| Target Milestone: | 2.6.1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | Obsolete | ||||||
| Attachments: |
|
||||||
In this case, both sub-datasets has a script computed column. and both of them use the same variable "index". Currently, the process of preparing joined dataset is first, we prepare some metadata of both datasets and then execute until the execution is needed such as dataset preview. since both datasets use the same variable and they will be considered as a global variable in the same scope of jointdataset, when execution, after the first dataset is executed, the variable value will be kept. and when the second dataset is executed, this kept value will be used. We use the new logic after the fix of bugzilla bug 235707. And the current process is more reasonable than preparing one data set, execute it and preparing the second and execute. It is an order issue, Users should use different variable names if they want to support this case. so set this issue as invalid. Verified. |
Created attachment 168348 [details] Report Description: 1, Each dataset including a computed column: name: index; type:integer; expression:0 2, Specify the script of datasets to: beforeOpen: index=0; onFetch: row["index"] = index; index++; 3, Join the two datasets Build number: 2.3.2.v20100115-1545 Steps to reproduce: 1, open the attached report design 2, open the joint dataset and preview Actual result: Result is null.