Issue with report data - New_WI_Count
Hi,
I'm trying to develop a report(a simple table) that gives me a count of the WorkItems that are created each day. I'm sure that I need to use the NEW_WI_COUNT snapshot to pull this data.
Now, here is the issue. When I display just the TIMESTAMP and WI_COUNT, it gives the correct result with the latest snapshot as the last row. But if I add another column say CATEGORY_NAME , it doesn't display the complete result set and the last row shows a previous snapshot date.
I'm using RTC 1.0.1 and BIRT 2.2.2
Please help me with this.
Thanks,
Bharath
I'm trying to develop a report(a simple table) that gives me a count of the WorkItems that are created each day. I'm sure that I need to use the NEW_WI_COUNT snapshot to pull this data.
Now, here is the issue. When I display just the TIMESTAMP and WI_COUNT, it gives the correct result with the latest snapshot as the last row. But if I add another column say CATEGORY_NAME , it doesn't display the complete result set and the last row shows a previous snapshot date.
I'm using RTC 1.0.1 and BIRT 2.2.2
Please help me with this.
Thanks,
Bharath
7 answers
When you display the reports in the BIRT Report Designer, there is a limit on the number of rows you get in each data set. Try Deploying the report to the jazz server and you will get better results. Need to watch out for the size of the data you are retrieving.
I see the same issue on the Jazz server aswell. Also, I have this issue with predefined reports aswell. For example, if I view New Work Items By Severity it doesn't provide me the latest snapshot data.
Yes we made numerous changes to the report templates and our data collection code. The new report templates were re-written using a newer version of BIRT (2.3.2.2) and the data collection tasks now take much less time to run (1/10 th).
After migrating to 2.0 from 1.0, some of the data warehouse tables will emptied. But the first run of the nightly tasks will rebuild that data. So expect that to take a few hours to complete. You can keep an eye on the task in the Active Services admin page.
After migrating to 2.0 from 1.0, some of the data warehouse tables will emptied. But the first run of the nightly tasks will rebuild that data. So expect that to take a few hours to complete. You can keep an eye on the task in the Active Services admin page.
Yes we made numerous changes to the report templates and our data collection code. The new report templates were re-written using a newer version of BIRT (2.3.2.2) and the data collection tasks now take much less time to run (1/10 th).
After migrating to 2.0 from 1.0, some of the data warehouse tables will emptied. But the first run of the nightly tasks will rebuild that data. So expect that to take a few hours to complete. You can keep an eye on the task in the Active Services admin page.
Thanks for the info Rafik