Sorry, but we don't know if it can even be achieved using additional front-end development. The only solution we can think of is adding a column to the view you already use where the calculation will be performed automatically and displayed in the pivot table.
In the basic configuration, there is no option to display all rows as collapsed by default in the pivot table functionality. We have noted this idea to our R&D team. You might consider implementing a fixed style for lists using development tools.
I apologize for the misinformation. You will not be able to implement this through development because the pivot table is a web component and cannot be overridden.
I do wish we could add dashboard list elements on pages. It would make things easy to display unrelated data on a page and things like pivot tables. However, I don't believe there is anyway to add it to the page that I know of. We usually just create a view, then display the results in a detail on the page instead. For creating a pivot table, Postgresql does have the crosstab function which does this easily - However, that is part of the tablefunc extension, which isn't installed in Creatio postgresql databases - I've never tried to see if it allows you to install extensions like that. See https://stackoverflow.com/questions/3002499/postgresql-crosstab-query/1…
I setup Pivot table on Portal main page. And in setup it is displayed like Pivot. But when I login as portal user, I see this data like simple list. Is it possible to display Pivot on Portal?
Thank you for bringing this question to us. By default portal users can't see Pivot tables for several reasons. First of all - they should have a feature PivotTable active (this can be done on https://YOUR_WEBSITE_DOMAIN/0/Features page).
The second reason can not be overcome in the actual version, I am afraid. It will be solved in the 8.0.7 release. Pivot tables have a different directory from other dashboards. Their path is not available for Portal users as of now.
As in the embedded screenshot, the Achieved Rate column (using the "Average" method to calculate totals) does not reflect the correct value of Opportunity amount column / Budget column. In this case, the row of month 8 contains 2 records of opportunities, but its Achieved Rate column value 0.83 is not 249,600/306,798; instead, 0.83 is the average of the 2 ratios of Opportunity amount/Budget of those 2 opportunities.
How can I do to display the value of 249,600/306,798 ?
At first, you can try to change the type of calculation from the "Average" to others for the 'Achieved Rate' column (for example set "Amount" to see how the calculations will be changed). Also you can compare the accuracy of the formula you use if you check the report of the needed records in excel. For that you will need to find the needed section (Opportunity), open the needed records/details for the 8th month, and export those records to excel. After that you will be able to re-check the value you received in the pivot table with the value you got in the excel report for the same period.
Also in the article below you can find more information about the formulas that are being used in the system:
Thank you for your reply. But it didn't answer my question.
As the screenshot below, you can see there is obviously no appropriate item to calculate what I need, and of course I had tried every item and no result was right.
On the other hand, I found that in the Forecast section, the (pivot) table shown there is correct! I added a new forecast "FORECAST BY OPPORTUNITY" as shown below, and you can see the three Achieved Rates of the last 3 rows are correct respectively under the 3rd quarter of 2021.
When opening the dashboard, the user would like to see
instead of
... then he would drill down or not, as needed.
(the user does not want to see all the detail at once, only the totals. Every time the dashboard is opened he has to roll everything up (collapse), in order to focus only on the big numbers)
The pivot tables are created as Angular components that cannot be changed through the base functionality in the configuration section. However, such a request is already registered and will be implemented in the nearest releases.
