Dear community,
We are in the process of migrating Pivot Tables to the Modern UI and would like to collect some feedback and information about the usage scenarios.
In the Classic UI, there is an option to create a pivot table directly from a GI as a GI’s tab or to go to the SM208010 Pivot Tables form and create a pivot table as a separate form with its own Screen ID and a menu item.
Can you please share your usage scenarios for the second option? (pivot table as a standalone form)
+2Honestly, the only scenario that I have used direct pivot tables is to assist with creating links direct to those pivot tables to send to users. If the data is filtered by a parameter, such as Sales Profitability Analysis, it is better to have it as a tab on the GI.
A dashboard can show a pivot from a GI, which could replace that usage scenario.
Linking to a shared filter would go direct to the pivot table - Maybe that exists and I don’t know how to use it?
Honestly, the only scenario that I have used direct pivot tables is to assist with creating links direct to those pivot tables to send to users. If the data is filtered by a parameter, such as Sales Profitability Analysis, it is better to have it as a tab on the GI.
A dashboard can show a pivot from a GI, which could replace that usage scenario.
Linking to a shared filter would go direct to the pivot table - Maybe that exists and I don’t know how to use it?
Thank you for your feedback, Keith! Direct linking to a filter is not in the product yet but we have this idea in the backlog.
Like Keith, being able to send links directly to pivot tables would be useful for us. Similarly, being able to use a direct link to a pivot table as a Acumatica menu item is also helpful: Sometimes a GI results grid is useless, but a pivot table based on the data therein is gold.
+1We’ve never found tremendous value from PivotTables, as we’re kind of sticklers about formatting (also haven’t every spent much time trying to make them look good). We typically will instead do a GI with groupings that summarizes the data in the most user friendly form, and then use side panels to expose details as needed.
My only use case for the second option - a stand alone form - is when I use the same GI as a source for multiple pivot tables (to slice the same info multiple ways) Otherwise it's too much of a pain to make adjustments to a stand alone pivot table.
If adjustments are being made to pivot tables, hopefully users will be able to conditionally format a pivot table in the new version, like we can currently do with a GI.
I’ve been implementing Acumatica for close to 5 years and I can’t say I ever use the Pivot as a Standalone Form. Like others were saying, it’s much easier to incorporate the parameters and different groupings of the “same” pivot table with just using separate saved tabs in the main GI.
+3I have used both the standalone Pivots and the incorporated in the GI versions for the clients.
The standalone version is also useful if there is a need to expose the Pivot to a dashboard.
In general, I would say that most of the time we are able to build the needed data view with the GI itself, likely 80% of the time. In the other 20%, most of the time it is incorporated Pivot - like 70% or so.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
