Completed
Last Updated: 27 Jun 2023 14:18 by ADMIN
Philip
Created on: 12 Jun 2023 06:50
Category: PivotGrid
Type: Feature Request
6
PivotGrid overall functionality

Hello

Just testing the new PivotGrid and a few features seem missing which may be critical and I cannot see an easy way to customise via templates or the like.
Apologies in advance if I have just missed it in the documentation or my understanding.

In my opinion, the main purpose a developer would put a PivotGrid into a web application;

  • To simplify data "slicing and dicing" for users not comfortable with tools such as Excel/PowerBI, and reduce the need to export to Excel.
  • To synchronise a pivotGrid view with other components/controls and/or charts on the page

 

Critical

  1. No width parameter: This seems quite critical for general formatting purposes
  2. No mouse hover: Considering there is no width parameter, then there should at least a mouse hover so that the user can hover to see content which has been cut-off due to insufficient width (like the TelerikGrid).
  3. Defer Layout Update: By default the telerik PivotGrid is always deferring the layout change. Usually on PivotGrids (Excel / PowerBI) there is a tick-box to allow the user to choose. For performant pivot tables, there is no need to defer the layout allowing for quick anaytics.
  4. No "Title" attribute or alias for xmla fields: There is no property to rename fields in the xmla dataset, so the user needs to see the full [Table].[ColumnName] attributes in its raw form (which ends up being quite ugly and potentially confusing for the user).
    eg: <PivotGridRow Name="[Product].[Category]"></PivotGridRow>
  5. No event handlers: I cannot see any event handlers at all on this control? There are many user-triggered events which could be triggered within the GridConfigurator. This would be critical to synchronise the PivotGrid with any other controls, with the PivotGridEventArgs holding data of what was modified and if the modification was made to the PivotFields or Measures.
  6. No state management: Cannot save or restore state of GridConfigurator. Potentially, the user may have spent some time setting up their perfect PivotGrid that suited their needs, hence saving state seems critical.
  7. No programmatic control via @ref="PivotGrid": Cannot programmatically control the PivotGrid. This would be important to enable synchronisation between other Telerik controls / items on the page.

 

Less Critical

  1. Export: Not critical but some form of export (Excel/PDF), to allow user to save the results.

 

Aside from that, all good and works well.

 

Cheers
Phil

5 comments
ADMIN
Nadezhda Tacheva
Posted on: 27 Jun 2023 14:18

Hi Philip,

We've revised the requirements and I have opened dedicated items for them as I mentioned in the meeting. You can find them as follows:

  1. No width parameter: https://feedback.telerik.com/blazor/1614147-column-width.

  2. No mouse hover: as clarified during the meeting, the general purpose of this request is to somehow allow the user to see the whole cell value. This scenario will actually be covered by the Width parameter and the ability to resize the columns.

  3. Defer Layout Update: https://feedback.telerik.com/blazor/1614148-defer-layout-update.

  4. No "Title" attribute or alias for xmla fields: https://feedback.telerik.com/blazor/1614149-title-parameter-for-the-rows-and-columns.

  5. No event handlers: as discussed during the meeting, you need events fired when the user makes changes in the configurator - e.g. add row or column, filter some data. I synchronized this with the team and I can confirm that such operations will be tracked through the state similar to the OnStateChanged event in the Grid.

  6. No state management: https://feedback.telerik.com/blazor/1614153-state-management.

  7. No programmatic control via @ref="PivotGrid": currently, the PivotGrid exposes a Rebind method that allows processing the component Data and refreshing the UI. Additionally, programmatic control will be possible through the state.

  8. No ability to change the aggregate (sum/min/max etc) of measures at run-time: https://feedback.telerik.com/blazor/1614157-ability-to-change-the-measure-aggregate-at-runtime.

  9. No control over sub-total and total visibility: https://feedback.telerik.com/blazor/1614160-sub-total-and-total-visibility.

  10. Missing visual indicator for sorting: https://feedback.telerik.com/blazor/1614154-visual-indicator-for-sorting.

I added your vote to all of these items. As a creator, you are automatically subscribed to receive status updates.

I will now close the current thread as completed since we will address and track the features in the dedicated items.

Regards,
Nadezhda Tacheva
Progress Telerik

As of R2 2023, the default icon type will be SVG instead of Font. See this blogpost for more information.
ADMIN
Stamo Gochev
Posted on: 26 Jun 2023 06:05

Hello Philip,

My colleague Lyubomir informed me that you have already addressed the questions that you had during a meeting. We will sync with Lyubomir about future actions that we can take because of your valuable feedback.

Regards,
Stamo Gochev
Progress Telerik

As of R2 2023, the default icon type will be SVG instead of Font. See this blogpost for more information.
Philip
Posted on: 19 Jun 2023 00:43

Hi Lyubomir

 

Yes - anytime during business hours (9-5) - my timezone is Singapore (GMT +8).
paquilina@aquip.io

 

 

Thanks
Phil

ADMIN
Lyubomir
Posted on: 16 Jun 2023 12:16

Hi Philip,

Thank you for your valuable feedback so far! As the Product Manager for Blazor, I am sincerely interested in hearing your thoughts directly. I would like to schedule a brief call with you to gain deeper insights into your PivotGrid scenario and application. If you're comfortable with it, we can arrange a meeting at a time that suits both of our schedules. Could you please suggest a few days and time slots that work for you? Feel free to provide your availability, and we'll coordinate accordingly.

Regards, Lyubomir Atanasov

Progress Telerik

As of R2 2023, the default icon type will be SVG instead of Font. See this blogpost for more information.
Philip
Posted on: 12 Jun 2023 07:08

Just to add to the above critical list;

 

8. No ability to change the aggregate (sum/min/max etc) of measures at run-time: Standard pivot table feature
9. No control over sub-total and total visibility: Standard pivot table feature
10. Missing visual indicator for sorting: There is sorting which works well, but no visual indicator to show to the user the current sort (like the TelerikGrid).