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.
Solved! Go to Solution.
You would need a Premium workspace and the concept of an app (and only sharing the app) to accomplish this pseudo staging setup. However we have found that oftentimes meta data changes in the PBIX are severe enough to cause disruption in the app unless we also republish/update the app.
One other way to test would be to have a shadow PBIX that has the new functionality but is only shared with test users. Once they are happy the shadow PBIX can be "saved as" the "production" PBIX.
Thanks @lbendlin.
I like the concept of the App. I'm using that in other Workspaces.
The sync with SharePoint, to me anyway, doesn't seem like a great idea due to the limitation I mentioned in my original question. We wanted to ask our users to do this as a best practice, but actually I'll just ask them not to sync it with SharePoint, but still store the PBIX file in a SharePoint folder so that they can use the version and restore functionality... and simply click Save as they make edits and Publish when they want to commit them. People are used to that process anyway.
Thanks for all your help,
Garry
You would need a Premium workspace and the concept of an app (and only sharing the app) to accomplish this pseudo staging setup. However we have found that oftentimes meta data changes in the PBIX are severe enough to cause disruption in the app unless we also republish/update the app.
One other way to test would be to have a shadow PBIX that has the new functionality but is only shared with test users. Once they are happy the shadow PBIX can be "saved as" the "production" PBIX.
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.
User | Count |
---|---|
107 | |
93 | |
77 | |
65 | |
53 |
User | Count |
---|---|
147 | |
106 | |
104 | |
87 | |
61 |