Hello,
i am evaluating the xamPivotGrid and just a few questions are remaining:
Thanks,Dennis
Hi Dennis
About your questions
1. You can use DataSource’s collections to listen to collection changes
pivotGrid.DataSource.Columns.CollectionChanged += Columns_CollectionChanged;
pivotGrid.DataSource.Rows.CollectionChanged += Rows _CollectionChanged;
pivotGrid.DataSource.Filters.CollectionChanged += Filters _CollectionChanged;
pivotGrid.DataSource.Measures.CollectionChanged += Measures _CollectionChanged;
2. In that version of XamPivotGrid, it does not support paging. But it supports virtualization and memory consuming is low, and performance is very good.
3. We have internal property about MDX query. If you think it is useful we can think about the future o
4. You can drop more than 1 measure in pivot grid. If I don’t understand you please describe in more details .
5. You can access member by header cell. Member property. What kind of attributes do you want to get?
Regards
Todor
Hello Todor,
i just realized that the "Measure"-Object is also appearing in the Excel Pivotgrid. So using more than 1 Measure is indeed possible, i just have to ignore the "Measure"-Object when iterating over the header Columns.
So the cube problem is still remaining. I had 3 databases (A,B & C) that i could select in the XamPivotDataSelector. Each database contains one cube, but no cubes for the databases B&C appeared in the DataSelector after having selected these cubes. So i removed database A from the sql server. Now i can select the cube from database B, but the cube for database C is still missing in the DataSelector
Regards,
Dennis
.
Hello Dennis,
I am just checking if you got this worked out, and if you still require any assistance or clarification on the matter.
If this is what you were looking for please verify the answer so it helps other users as well.
Sincerely,Petar MonovDeveloper Support EngineerInfragistics Bulgariawww.infragistics.com/support
Hi Petar,
i still require asistance for the cube problem.
Regards,Dennis
If you mean the problem that occurs when more than one database is ran on the server it's due a bug in the request that is sent to the server. In this scenario the server expects some additional settings when querying data from databases that are not on the top but works well for the latest one. We have fixed it and it will be included in next service release.Thank you for your assistance while clarifying this problem. I hope that issue wouldn’t stop your work at all.
Regards.Plamen.
When is the next service release going out?