It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787

question asked: Jul 27 '09, 11:25 a.m.
question was seen: 5,081 times
last updated: Jul 27 '09, 11:25 a.m.

Related questions

FAQ - How this Forum works

Migration issue to RTC 2.0 solved: report data types

0
Timothy McMackin (153●10●6) | asked Jul 27 '09, 11:25 a.m.
JAZZ DEVELOPER
I encountered an issue with migrating a report from RTC 1.0.1 to RTC 2.0 and I thought I'd report it here. There's an easy workaround, but I thought that other people might see this issue. Please let me know if there is somewhere else I should report this.

I had a BIRT report in RTC 1.0.1 that listed some work items. The report's data set got the work items' ID numbers as a String data type, which was the default when I created the data set in RTC 1.0.1. In the report code, it looked like this: 

<oda-data-set extensionID="com.ibm.team.reports.generic.dataSet" name="My work items" id="17">

<!-- computed columns snipped for clarity -->

<list-property name="columnHints">

	<structure>

		<property name="columnName">WI_ID</property>

		<property name="displayName">WI_ID</property>

	</structure>

<!-- other data column aliases snipped for clarity -->

</list-property>

<structure name="cachedMetaData">

	<list-property name="resultSet">

		<structure>

			<property name="position">1</property>

			<property name="name">WI_ID</property>

			<property name="dataType">string</property>

		</structure>

<!-- other data columns snipped for clarity -->



It seems that in RTC 2.0, the work item ID is provided as an Integer. Since my data type still specified String, RTC (or BIRT, not sure which) converted the work item ID to a comma-delimited string. So work item 12345 became work item "12,345", and that broke some of my code that wasn't expecting commas. (For example, linking to work item "12,345" sends you to work item 12.)

The BIRT report editor will not allow you to change the data type of a column (I had tried changing WI_ID from String to Integer on the Output Columns page of the BIRT data set editor with no success). So I fixed this manually by editing the XML source directly and specifying the integer type: 

<property name="dataType">integer</property>


I had to correct this line in two places per data set. Then, I had to correct the column's data type on the Binding tab of the Property Editor view to use an integer on the report page itself.


That solved the problem and got my work items listed as "12345" rather than "12,345."

Edit: updated code blocks; the XML code didn't get displayed right hte first time.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
James Moody (3.3k●2●4) | answered Jul 27 '09, 2:14 p.m.
JAZZ DEVELOPER
Hi tmcmack,

Thanks for the commentary on this. I'd like to add this (or a paraphrase
of it) to one of our FAQs in case others are confronted with a similar
issue, would that be okay?

james
RTC Reports Team Lead

On 7/27/2009 11:38 AM, tmcmack wrote:
I encountered an issue with migrating a report from RTC 1.0.1 to RTC
2.0 and I thought I'd report it here. There's an easy workaround, but
I thought that other people might see this issue. Please let me know
if there is somewhere else I should report this.

I had a BIRT report in RTC 1.0.1 that listed some work items. The
report's data set got the work items' ID numbers as a String data
type, which was the default when I created the data set in RTC 1.0.1.
In the report code, it looked like this:

oda-data-set
extensionID="com.ibm.team.reports.generic.dataSet"
name="My work items" id="17"
!-- computed columns snipped for clarity --
list-property name="columnHints"
<structure
<property>WI_ID</property
<property>WI_ID</property
</structure
!-- other data column aliases snipped for clarity --
/list-property
structure name="cachedMetaData"
<list-property name="resultSet"
<structure
<property>1</property
<property>WI_ID</property
<property>string</property
</structure
!-- other data columns snipped for clarity
--


It seems that in RTC 2.0, the work item ID is provided as an Integer.
Since my data type still specified String, RTC (or BIRT, not sure
which) converted the work item ID to a comma-delimited string. So
work item 12345 became work item "12,345", and that broke
some of my code that wasn't expecting commas. (For example, linking
to work item "12,345" sends you to work item 12.)

The BIRT report editor will not allow you to change the data type of a
column (I had tried changing WI_ID from String to Integer on the
Output Columns page of the BIRT data set editor with no success). So
I fixed this manually by editing the XML source directly and
specifying the integer type:

<property>integer</property>


I had to correct this line in two places per data set. Then, I had to
correct the column's data type on the Binding tab of the Property
Editor view to use an integer on the report page itself.


That solved the problem and got my work items listed as
"12345" rather than "12,345."
0
permanent link
Timothy McMackin (153●10●6) | answered Aug 12 '09, 2:28 p.m.
JAZZ DEVELOPER
Sure, go ahead and add it to the FAQ or anywhere else you might want to post if if you think people would find it useful.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.