Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Has anyone else experienced Report Builder output incorrectly cutting off attribute text.

 Has anyone else experienced Report Builder output incorrectly cutting off attribute text. Should the output not match the actual contents of the attribute text?

0 votes

Comments

Hi Daniel,

Can you make it more specific?
1. What data source (DWH or LQE) are you using?
2. What database are you using?
3. In what application and what attribute do you see this problem?
4. How many characters are shown in RB, and how many actually in the source application?

For example (DWH), number of maximum characters for RTC workitem is 255 for name and 1024 for summary attribute by default. This is the size allocated in the database.



2 answers

Permanent link

 Answer in bold underline


 Can you make it more specific? 
1. What data source (DWH or LQE) are you using? DWH
2. What database are you using? DOORS Next Generation Requirements Managment
3. In what application and what attribute do you see this problem? String
4. How many characters are shown in RB, and how many actually in the source application? cutoffs are around 250 - 255 characters in length on report builder, varying lengths > 255 characters at source.

For example (DWH), number of maximum characters for RTC workitem is 255 for name and 1024 for summary attribute by default. This is the size allocated in the database. 

0 votes

Comments

So is this a requirement's custom attribute with String type?

Please open Advanced tab and see the SQL query. If the data is coming from table RQRMENT_STRING_EXT, then the maximum characters in this table is 255, while RQRMENT_STRING_L_EXT is 4000.

Check which table name is used for your SQL query. Basically it is determined by custom attribute settings in DNG. Have you made any change here before (eg. change attribute type from String to String (L))?


Permanent link

Verifying further,,, I find there is no such String (L) custom attribute in Requirement. There is only one String type in RM requirement, and it uses RQRMENT_STRING_EXT (maximum 255) in DW. This is the cause.

It looks like this is a known issue and the workaround is to extend the size of VAL column in RICALM.RQRMENT_STRING_EXT to 1024 or whatever needed. Then run full DCC job to reload the data. If your database is on premise, then report it to your DB admin. If your database is in cloud, then create a ticket to IBM or Zendesk to ask for it.

0 votes

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Jun 10 '18, 9:32 p.m.

Question was seen: 2,254 times

Last updated: Jun 12 '18, 3:48 a.m.

Confirmation Cancel Confirm