I've often faced the situation of being given a REPORT, often a pivot of some kind, on which to perform some analysis for the boss. And that's a challenge for a spreadsheet user, because rather than using data in columns, now you also have data in rows. Very dicey! Not to mention the spreadsheet problems related to wrapped rows with headings in multiple rows or multiple row types with headings in multiple rows.
Bottom line: reports make lousy analytics.
Reports are made to tell a story at a glance. Something a manager or VP might find useful. If you've got to dig beyond that, your source should not be a report. It should be the place from which the report originated or beyond.
In almost every instance that I pulled data from business objects (stuff I could not get from our old Oracle databases) I exported a .csv simple table that I imported into my report tool (Excel) for analysis and reporting. If anyone needed DATA, I could give them the .csv to work with, NOT A REPORT!
It's is a waste of time to try to use a report to dig for data!
Skip,
[sub]
Just traded in my OLD subtlety...
for a NUance![/sub]
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.