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

Why do I only get 200 records out of 252 when I export a RRC view to CSV?

I have configured a view in RRC. The query is based on internal fields and custom fields.

If I export this view to Excel I get only 200 (each time exactly 200) records. On the UI I get 252 records.
I can add or remove records from the view. The UI shows theis changes, but the export still exports 200.

Is there somewhere a configuration parameter which limits the export of RRC to CSV to 200 records?

Additional Info:
I had a look into the attribute filter of the view. The special thing there is, the filter is done on information of a linked requirement. See:

RRC Filter of problematic view

0 votes

Comments

Guido, the RTC Server has a query result size limit. This might be a similar case.

In RTC there is an advanced property to change the limit.

I gave it a try today and couldn't figure a parameter for it. Converting this to a comment and hope someone else can shed some light on it.

Thanks Ralph,

I think it is not a limitation. I tried some other views and they are working and give more than the 200.

So ot looks like the query of this view is a problem. It's the same view which needs more than 25 minutes to run (other question in this forum).

I think this question can be closed.

Hi Guido,
Which version of RRC are you using?
Tom

I don't suppose you know what is the 201st row to be exported from the view and whether you can export only that artifact?

I am wondering if there is something in the artifact content that is causing the export to fail.

I'm using v.4.0.1.

@Robin, this is a good idea. I try to find out the 201th. Because I get the 200, I know also the 52 missing. Maybe the are somhow sorted and it's the first of them or I find a pattern in the missing 52.

It's also interesting, that the view needs 60 seconds to load on UI and 25 minutes to export to excel. Another view with more than 1000 records is done in a few seconds.

showing 5 of 6 show 1 more comments


One answer

Permanent link
We just saw a similar issue with another customer who had just upgraded from 3.x to 4.x.  They had completed the upgrade, but had not restarted the JAZZ server following the upgrade.  Once they restarted the server, the issue went away.  Have you tried restarting the JAZZ server?

0 votes

Comments

We updated a month ago to 4.0.1 and have rebooted several time.

Do you have the JAZZ server configured to run as a service, and if so, did you manually shut down the JAZZ service prior to rebooting, or have you attempted to manually stop the JAZZ service and then restart it using the "Stop the Jazz Team Server" and "Start the Jazz Team Server" commands? 

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: Feb 04 '13, 12:08 p.m.

Question was seen: 5,188 times

Last updated: Feb 13 '13, 8:52 a.m.

Confirmation Cancel Confirm