Forum Discussion
Workspace Management Best Practices
Many documentations and videos you can find on the internet to answer your first question
Hi datapal04
Best practice is to seperate Reports(Thin Reports) from its Semantic models :
- Create 3 Workspaces: WS_DEV&Test , WS_Dataset_Prod(Could containt only Datssets or both) , WS_Report_Prod (Thin reports
- Use AD security groups to add to WS and share reports in App,
- Members and collaborators can only publish in WS_DEV&Test
- Create App from WS_Report_Prod
- Add reports into different Audiences in App environment
- Add security groups to specific audiences
Hi aj1973 , thanks for your reply! What's the reasoning for seperating reports from their semantic models?
I was also thinking that naming conventions can help with determining which reports and semantic models are production-ready (ex. "PROD_Test Report"). What does everyone think of this approach?
Many documentations and videos you can find on the internet to answer your first question
Hi,
Indeed, naming convention is defenitly a good help. Here is documentations and video for help.
To answer your first question :
Separating reports from their semantic models is a best practice in Power BI workspace management. This is because it allows for better control over the data and the reports that are built on top of it. By separating the two, you can ensure that the data is accurate and up-to-date, while also allowing for more flexibility in the creation of reports. Additionally, it makes it easier to manage the different components of your workspace, as you can focus on each one separately. Deleting or removing an Item from a WS by mistake can be very inconvinient because there is no way to restore it, Having the same item in 2 different WS with limit access helps recover it...
Here is some other disadvatanges of not separating items :
https://biinsight.com/thin-reports-what-are-they-and-why-should-i-care-and-how-can-i-create-them/
