Disable export of underlying data

[dmg1]

We are using SSAS Tabular as our datasource and we have issues when users try to 'Export underlying data' from the Power BI Service. The query generated to SSAS when doing this seems to include every measure from the table which in some cases is 30+ measures and sometimes from multiple tables. The query never completes and consumes nearly all resources on the SSAS server. We need to disable this option while still allowing export of summarized data.

[sokatenaj]

This is huge. If we can please get this as a security addition to the tenant settings, it would me much appreciated. If I drag/drop certain fields into a table or visual, then that is truly all I want people to see unless I make it known to them. We really need this as a feature to be turned off. I want more control.

[pbiideas1]

Agree we use PowerBI dashboards and provide all staff access to summarised data. Would be great if we could enable only the summarised view as underlying provides too much data and further there are limitations in the amount of data a non-pro user can export.

[dschmitz]

I work in a school district and want to share summarized data for Free/Reduced lunch in many reports, but cannot have users of the visualizations able to download the student level data records with Free/Reduced status attached. At the same time, the ability of school district staff to download the underlying summary data is central to the value Power BI brings to our district. PLEASE create separate export functionality controls for the Summary versus Detail export functions. Thanks!

[DavidCallander]

The MDX this generates is crazy, and as noted it consumes nearly all resources on the SSAS server. I'm working for a large Professional Services organisation, with a large and complex Cube with heaps of Measures, and we can't have our SSAS server getting killed for all the Partners and Directors, just because one of hundreds of users clicked on "export of underlying data", when all they really wanted was covered by "summarized data".

[JANETAKOS]

Agreed with comments here. I think this helps solve some column-level security challenges because we can write code that if a certain user is in the report that they see a "-" for a certain field like salary. Given that underlying data is an option when there is an aggregate it defeats the person of it.

[cbenson1]

We really needs the ability to export summarized data but not the underlying data. Would be ideal if the dataset owner, the individual we creates RLS roles in desktop, could control the level of detail (summarized or underlying) a user could export opposed to the system admin. Currently we have to turn off all export abilities which is extremely limiting - please fix this!!!!

[chr9219]

I agree with the others on here. We only want the users to see the summarized view and not the other sensitive data that can be seen in the underlying data export. Will there be a solution to this any time soon?

[ranash]

We need to be able to secure the underlying data. Some reports summarize highly sensitive data and while I need them to be able to export summaries the underlying data should be hidden. This should also be an option that is controlled report by report and group by froup.

[andritt]

this will be a huge help in our dashboard // especially if we share the report externally

[pbiideas1]

I would suggest some greater granularity to enable/disable summary & detail exports in the Admin Portal. Additionally separate enable/disable controls for Analyze in Excel