How to manage report deploy based on data sources with sensible data

[arimoldi]

Hi,

I have developed a dashboard on Power BI based on an fake / anonymized excel file stored in a Sharepoint folder; now the dashboard is ready and I have to deploy this dashboard in the production workspace.

The point is that I have developed this dahsboard using a fake / anonymized excel file and once the dahsboard will be in the production workspace it should be connected to the real file with sensible data that I cannot see / read and on which I should not have access.

How can I manage the deploy of this dashboard and the connection to the new source without reading or having access to the real file with sensible data?

Thanks,

Andrea

[tzvetkov_b87]

Hi @arimoldi ,

Agree with @Idrissshatila . You should get somebody with access to the datasource to publish the Power BI report. 

It would also help in the future if any updates and maintenance needs to be carried out - since you don't have access to the Data Source, you won't be able to make any changes in the Power Query.

[Idrissshatila]

Hello @arimoldi ,

they should have the same table names and column names as in the production, it's case sensitive as well.

[arimoldi]

Hi,

yes they have the same column names, structure and data type.

Reading your answer I think I didn't explain well the problem: how can I deploy a report in the production environment without having the access on the data source?

Thanks,

Andrea

[Idrissshatila]

@arimoldi ,

you need to reference the new datasource in the power query source.

[arimoldi]

that's correct, but it is not enough, because I have no access to the new datasource since it contains sensible data that I cannot access/read, while the dashboard was developed on test/fake data.

This is the error that I get when I connect the new datasource to the dashboard in Power BI Desktop:

Any other suggestions?

Thanks,

Andrea

[Idrissshatila]

@arimoldi ,

then someone that has access to data should replace the source, there's no other solution

[arimoldi]

unfortunately this is not possibile and not compliant with our Company structure, because people that have access to those file are from business, they have no technical skill and they don't have Power BI installed.

I can't believe that in the Power BI architecture there is no way to develop a report on file with fake / test / anonymized data and then switch the connection to the real file in the production workspace.

Any other suggestions?

Thanks,

Andrea