WebIntelligence Report’s Save As CSV Has a Problem?

Like a good obedient BO disciple I switched from using BO 6.5’s “full client” (now called Desktop Intelligence) to using BOXI’s Web Intelligence tool (also called WebI). To Business Objects’ credit, they have put much of Desktop Intelligence’s functionality in to WebI. But there is one disorienting difference.

BOXI Web Intelligence “Save to CSV” Is Different

My recollection tells me that if I exported a BO 6.5 Full client report to CSV that I received a CSV file with the same content that I would get through a Microsoft Excel export. Sure formatting, such as colors, column width, font, etc. were lost, but the order of the columns and even the report level variables in the table were exported to CSV from full client. Maybe, I a wrong about this (please point this out if I am), but that is the way I and some colleagues remember it.

BOXI Web Intelligence (and perhaps BO 6.x Web Intelligence) also has the ability to export to a CSV file, but this export behaves very differently. This export behaves much like the BO 6.x “View Data” or the “Data Cube” functionality. The BOXI WebI CSV export is a dump of the exact results of the first query of the report just as they were received from the database.

WebI CSV is a Query Result Export, NOTHING MORE

When you export a WebI report to CSV you may not get what you expect. The results should be identical to those you would get if you took the query and ran it directly against the database. This may be disappointing to some because it does not include any report-level aggregation, calculations, sorting, breaks, character formatting, or column ordering. HOWEVER, if a report developer is debugging a query or a universe object this output can be invaluable. For example, it can quickly uncover issues (such as Cartesian products) that dimensions can hide in a table. There are many uses for this output.

Why Does WebI’s CSV Have This Limitation?

I don’t claim to have inside information, but I can guess at two reasons for this limitation.

  1. Report Development Debugging: I know I already mentioned this, but I really want people to use the CSV export to understand more about their query and report. This previously perceived limit is actually advantageous functionality in the right hands.
  2. Discouraging ETL Use of Business Objects: If CSV were to output the aggregation and calculated columns of a report it would be readily used by end users as an ETL tool (Extract, Transform, Load). Some users still use it this way, but large scale use would explode if CSV exports were more than query dumps.
  3. What Can I Do If I Want a CSV Export of My WebI Report Table’s Data?

    There is almost always a workaround. If you must have your table’s data in CSV format then the solution is simple: export to Excel, open Excel output, save to CSV. You’re welcome!

Enjoyed this post? Share it!


55 thoughts on “WebIntelligence Report’s Save As CSV Has a Problem?

  1. Thank you Doople. In fact what i want to tell with text delimiter is : when we save into .csv, we have to choose the quotation mark to indicate that the field is a text. In the same way we choose a comma, semicolon or tab to indicate that it is new column. I don’t want to have quotation marks in my .csv but it’s mandatory. Now I’ve got a second problem : the french characters like é,à etc is not displayed correctly when I open the .csv file in Excel. Does anyone have an idea how i can fix these 2 points? Thank you.

  2. Hi Evren, I think that you can set the character set in XI 3.1, but I don’t recall if this “CSV with options” setting is available in XI R2.

  3. Hi,
    We have recently created a method to schedule WebI reports to be saved to TXT and it works for any BusinessObjects version, either BO 3 or BI 4. It is a 4-step process that hopefully will fulfill your needs. You can take a look at http://bit.ly/TLPBCK, hope it is of use!
    Best Regards,

  4. Is there a possibility to restrict not to allow to be saved Infoview Reports to csv? In order users not to see the content of original query.

Leave a comment

Your email address will not be published. Required fields are marked *