Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have created datasets, reports, and dashboards using an on-premise direct query to sql server against my development environment. It is currently saved in My Workspace. My Workspace has a data connection to my development sql server. I have an additional workspace that I have associated to a different user with a different data source and I have the gateway installed on that sql server machine. I published my reports to my power bi workspace and created a content pack and made it available to my other workspace. I was able to retrieve the content pack, but when I run the reports they are still pointing to the original data source I was using during development. I apologize I am very new to this, but cannot figure out how to point my reports to the correct data source.
Solved! Go to Solution.
@lizrowden First, if you aren't use the Power BI Desktop for further report development. It will allow you to change the connection from Dev to Prod, whereas if you did everything in the Service, you can't update that data set connection.
Second. Lets call your Dev user DEV and your other user PROD
As the DEV report author you are sharing content with other people. In your case, you shared a Content Pack. The PROD user can see and consume the Content Pack, and will see the dataset/reports/dashboards that DEV created. The PROD dataset won't apply to the DEV Content Pack Shared. In other words, DEV is sharing DEV reports, and PROD is interacting with DEV objects.
If you want to change the reports to be prod, you need to either create them in the PROD account, or (if you built things in the Desktop) change the data source from dev to prod and republish to the DEV account...
I hope that makes sense.
TL;DR; Unless RLS or SSAS is used, the end users will see what the report author sees. They assume the permissions of the report authors credentials.
@lizrowden First, if you aren't use the Power BI Desktop for further report development. It will allow you to change the connection from Dev to Prod, whereas if you did everything in the Service, you can't update that data set connection.
Second. Lets call your Dev user DEV and your other user PROD
As the DEV report author you are sharing content with other people. In your case, you shared a Content Pack. The PROD user can see and consume the Content Pack, and will see the dataset/reports/dashboards that DEV created. The PROD dataset won't apply to the DEV Content Pack Shared. In other words, DEV is sharing DEV reports, and PROD is interacting with DEV objects.
If you want to change the reports to be prod, you need to either create them in the PROD account, or (if you built things in the Desktop) change the data source from dev to prod and republish to the DEV account...
I hope that makes sense.
TL;DR; Unless RLS or SSAS is used, the end users will see what the report author sees. They assume the permissions of the report authors credentials.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.