Exploring, modeling, predicting and reporting with SAS Visual Analytics and SAS Visual Statistics

Disable detailed data export on regional/geo map

Posts: 43

Disable detailed data export on regional/geo map

[ Edited ]



we built a report in VA which shows, among other things, a regional/geo map of customers; the underlying table is a huge dataset with all customers information, but on the map we only show their location grouped by region.

However, when a user right-click on such a map in the VA report viewer, the popup menu shows the option "export map" and in the form he can select the checkbox "detailed data" and download the entire dataset with all columns and rows!


This is a security issue since we don't want to let end users to access the dataset.

Is there a way to disable this detailed export?


[VA version is: 7.2]


Thank you


Posts: 384

Re: Disable detailed data export on regional/geo map

You cannot turn off the option to export detailed data but you can disable exporting completely by using the SAS Visual Analytics roles.

Posts: 43

Re: Disable detailed data export on regional/geo map

Thank you for you answer, however users should be able to use the export feature to export simple data to excel... So there is no way to keep export enabled while preventing the user to download detailed data?


The purpose should be that the user should be able to export only what he sees.


Example scenario: we have a table with REGION | CUSTOMER_ID; we want to show the distribution of customers on a regional map; hence, we create a report with a regional map with REGION and COUNT(CUSTOMER_ID): then, if a user wants to export this data to excel (i.e. to do something else) he should export only this grouped table in excel, and NOT the CUSTOMER_IDs themselves! This does not make sense for us since if we liked to let the user to export the entire data we would provide him with direct access to the table instead of building a report... Smiley Indifferent

A hypothetical solution would be to directly load in VA the grouped table REGION|COUNT, so 1) the regional map would keep working and 2) even if the user would download the detailed data, all he would get is the grouped table REGION|COUNT. However, this "solution" requires to add a middle step of preprocessing to trasform our table REGION | CUSTOMER_ID in REGION | COUNT(CUSTOMER_ID), and this is extremely unconfortable and for all big tables and reports we use.


What would you recommend?

Thanks a lot


Post a Question
Discussion Stats
  • 2 replies
  • 2 in conversation