6127
I have volumes of information to share with my teams that is best presented in tables and matrices. It would be a huge improvement if they were able to export the data from the visualizations and have the formatting in Excel match the formatting created within PowerBI.

This would be especially helpful for ongoing forecasting activities.
STATUS DETAILS
Completed

Feature has been released in public preview.

Comments

W

You can export to excel when using Inforiver and the exact same formatting that you see in Power BI is retained.


This includes


  • Order of columns
  • Entire matrix/specific row/column selections
  • Column names as edited in the visualization
  • Row-first/column-first export for matrix/tables with a large number of rows and columns
  • Number formatting such as decimals, prefix/suffix
  • Notes and annotations
  • and more.


Check out this video for more details.


W

It is a very useful feautre but it should let users to select using this Preview Feature as default or not.

W

The export works for "simple" table (thanks for that) however it still needs to be improved: Mixed up columns and hierachies confuse the result. It would be great to have the columns in the same order.

W

need to have this in desktop version

W

Definitely a big step forward but it does bring the 150k row limit to the forefront. Specifically, when exporting a matrix with a high number of columns (i.e. where month is in the column and 12 months of data is being exported), the 150k export limit seems to be enforced against the underlying data. The result is that the export may contain rows orders of magnitude below what was expected (only 12,500 lines can be exported in the 12 months example). May not be possible to apply the 150k limit to the final export in the current layout but as is it can often turn a quick pull of a single matrix into multiple time consuming exports.

W

This definitely needs more testing, I have tried this on a table visualisation that shows financial results. The first column comes from, what we call, a Spec table, that allows us to control the GL account groupings, the row descriptions and the order in which they appear. The rest of the columns are all measures that we have defined for our GL data to display Current Month and YTD Actuals, Budget, Variance $ and Variance %. When we export the report using this new option the Variance $ columns appear as the first 2 columns in the export, i.e. before the row descriptions, and the Variance % columns appear towards the end, rather than next to their corresponding Actual and Budget columns. The export also includes additional columns, showing information related to a table that is used for conditional formatting. I can see how this additional information may be useful, but wasn't the expected outcome.

W

Needs more testing before final release!

I have found for the default hierarchy in the matrix the columns are displayed in the order of the values/columns were "added" to the table rather than the order shown in the matrix. This means I am having to remove values from the table, saving and re-adding in the order I want them shown. a lot of bother especially with the formats on selected columns.

Interestingly if you expand a level then the column order reflects that shown after the additional column showing the next level. Surely if the display order has been evaluated for these levels it can simply be used for the default level.

W

Yes this is now working - however I agree with a previous comment - the columns are not exported in the order as per the order as the visualisation - which was very confusing. Otherwise was great to see this finally. Thanks!

W

This is great! It works for me so far in the service, but not on desktop (not listed in preview features). Will it be added to desktop as well? That's where I often do exploratory analysis. Thanks!

W

Thank you for the release. The export works, but can be improved on several aspects:
- if you export a table that contains columns and measures from different tables, the columns are not reported in the same order as in the visualization, but columns from one table are reported first, then there are the columns of the next table, and so on
- if conditional formatting is used for some fields of a table, when exporting the table, a column containing the value of the measure used for conditional formatting is also shown
- the names with which the columns are exported are those of the original table and not those established in the visualization
- if a matrix contains more than one row in the header (for example turnover 2021, turnover 2020, turnover 2019) and has the months as columns, once the table has been exported, the rows of the header are translated and become columns, developing the table horizontally
- If the fields contained in the matrix/table are decimal numbers formatted to have two decimal places, once exported they maintain the formatting of the original column (with many more decimals)
- The colors are not maintained, but this is rightly specified when you do the export.

I hope you find these tips useful for future updates. Thank you.