A
andy.novak
We have OLAP working with PS and it is acknowledged that without Admin
privileges, one cannot create a permanent OLAP view. And I don't
warm up to the idea of giving others that rigtht in the server. The
only thing a user can do once they finish their last drag and drop is
save what their model to an Excel spreadsheet, which can be saved to
their desktop and changed / refreshed later on because the data hooks
are still there.
A colleague of mine makes the following statements and I'd like to
know from others' experiences if this is really all true or if it's
just a matter of learning more about how Excel and pivot tables work.
See below....
Please comment on their comments and also comment on a 3rd party
reporting tool....
Thanks,
Andy Novak
UNT
"The issue is that the OLAP cube reporting is so much nicer and
problem free than using reports exported to Excel. For example, the
report that you originally created, when exported to Excel, lost its
ability to “expand” the left most column. I’m attaching a report I
made for user "xyz". It looks real nice, but if they want to drill
down to a specific team they loses her column formatting – just a
hassle you don’t have when you work directly from OLAP. Another quirk
I found is that, in OLAP, I could add or delete columns at will; for
example I originally had Task List Level 02 and 03 and exported it to
Excel. There I colored the columns to match the original report. I
then found that while, in OLAP, the whole report printed in portrait
mode, it was just too much to print in Excel, even in landscape. Now
here is the hitch, I could not delete Task List Level 03 as the field
list only recognized Task. So I delete Task (which deleted 02 & 03)
and reentered just Level 02, but then I lost my formatting . . .
Another thing is that, in Excel I tried to change the title
“RBS_R_Assignment” to “team” or something like that that was more
friendly, but since it was an integrated part of the pivot table I
could not (but could in OLAP). Also, column and row headers come out
in odd places; for example “actual work” was on the left and column,
when it was really a data items in the right columns (not so in OLAP);
I got around it by formatting the title in white, which effectively
made it disappear. The bottom line is that working in OLAP is quick
and fun and working in Excel in clunky and frustrating. The OLAP
reporting tool is such a nice tool, it’s a shame not to let it shine.
Do you know if there is a 3rd party reporting tool?"
privileges, one cannot create a permanent OLAP view. And I don't
warm up to the idea of giving others that rigtht in the server. The
only thing a user can do once they finish their last drag and drop is
save what their model to an Excel spreadsheet, which can be saved to
their desktop and changed / refreshed later on because the data hooks
are still there.
A colleague of mine makes the following statements and I'd like to
know from others' experiences if this is really all true or if it's
just a matter of learning more about how Excel and pivot tables work.
See below....
Please comment on their comments and also comment on a 3rd party
reporting tool....
Thanks,
Andy Novak
UNT
"The issue is that the OLAP cube reporting is so much nicer and
problem free than using reports exported to Excel. For example, the
report that you originally created, when exported to Excel, lost its
ability to “expand” the left most column. I’m attaching a report I
made for user "xyz". It looks real nice, but if they want to drill
down to a specific team they loses her column formatting – just a
hassle you don’t have when you work directly from OLAP. Another quirk
I found is that, in OLAP, I could add or delete columns at will; for
example I originally had Task List Level 02 and 03 and exported it to
Excel. There I colored the columns to match the original report. I
then found that while, in OLAP, the whole report printed in portrait
mode, it was just too much to print in Excel, even in landscape. Now
here is the hitch, I could not delete Task List Level 03 as the field
list only recognized Task. So I delete Task (which deleted 02 & 03)
and reentered just Level 02, but then I lost my formatting . . .
Another thing is that, in Excel I tried to change the title
“RBS_R_Assignment” to “team” or something like that that was more
friendly, but since it was an integrated part of the pivot table I
could not (but could in OLAP). Also, column and row headers come out
in odd places; for example “actual work” was on the left and column,
when it was really a data items in the right columns (not so in OLAP);
I got around it by formatting the title in white, which effectively
made it disappear. The bottom line is that working in OLAP is quick
and fun and working in Excel in clunky and frustrating. The OLAP
reporting tool is such a nice tool, it’s a shame not to let it shine.
Do you know if there is a 3rd party reporting tool?"