RRC Export Module to CSV - Ordering Results
Background:
I have 5 large modules containing tabular data that I need to export out of the database. This exported data will be formatted and published to a customer. I plan to export the data as raw CSV, then perform post-processing on the CSV files in order to format it in a presentable fashion.
Problem:
The data exported from the RRC Modules appears to be produced in quasi-random order. In other words, the sequencing of artifacts within the view of the RRC Module has no correlation to the actual sequencing of the rows generated in the output CSV.
Question:
Is there a way to enforce a particular sequencing of the output data in a CSV export of an RRC Module?
Accepted answer
What version of RRC are you using. Could you be running into the following? This was fixed in 4.0.3.
Order of requirements in CSV is not the order in the view (69752)
Hope this helps.
Comments
We are still on 4.0.1. Our admins have been promising to update us to 4.0.3 for a while now, but there have been delays. I'm glad to know that this is fixed. This should give me one more reason to push for the update. Thanks.
Hi,
Try by creating a view with the desired order, then right click on the view and select export to CSV. The exported CSV must maintain the view order
Comments
Nate Decker
Jun 24 '13, 12:22 p.m.It looks like there is a built-in attribute called "Section" which tracks the sequential relationships of artifacts within a module. Even if the data is exported randomly, I should be able to resort the resulting CSV file based on this "Section" value. That being said, this solution will require some unwanted complexity in my sorting algorithm since I have to include logic to prevent 0-20 from being interpreted as coming after 0-2 and before 0-3. I think most default comparison operators won't interpret this correctly.
It would be much preferred if I could export in a what-you-see-is-what-you-get sort of fashion.