I use the Office Web Component 2003 Pivottable in SharePoint but there are some bad behaviours.
- slow loading
- error messages like: An Error 0x0040200 occured
We use Reporting Services in most cases, but the positive aspects like Dynamic Dimensions and measure usage or Dynamic filtering in Hierarchies are to import to lose.
The Office Web Components are not developed anymore. In SharePoint Services 3.0 they can function, but it is not 100% the correct way. Does someone know the best way to use Pivottables in SharePoint Services 3.0?
Thnx
Hessel Appers
Hi,
I am using OWC 11 and it works perfectly for me,
although I am not using sharepoint, but have my own Asp.Net portal.
I am using OWC pivottables and pivotcharts.
OWC should be as fast as your BI studio/visual studio 2005 while loading/displaying or browsing a cube. (I believe)
because BI studio or Visual studio uses OWC.
If the performance is slower in both the cases, then it might be that you need to improve performance of your cube.
if the loading time is slower, try to display a filtered dataset or a higher level dataset,
the users can then drill down to the level required.
When using OWC, it is always better to show only the most required data and also the most minimum set.
This is because OWC is browser based, it would make IE take up a lot of memory,
and thus make IE slower, eventually your OWC component would also become slow with more data.
As an alternative to using OWC pivottables,
is to use the newer excel services (Microsoft Office 2005).
It jells best with sharepoint and is infact built to support sharepoint.
another alternative is to try other third party and free OLAP controls.
one free control that I can suggest is the "CellSetGrid".
The source code is also avaliable,
so you can look through it and make changes if required.
also the simple usage is pretty easy.
search for 'CellSetGrid' in google.
please do let me know,
how this comes, what you choose and what gave you best performance and features.
Regards
No comments:
Post a Comment