Forum Discussion
Deployment Pipeline help
Hi PPStar
Thanks for the clarification, makes sense. In that case, I suggest the following approaches:1) Use Dataset Endorsement -> In Power BI Service, datasets can be endorsed as "Promoted" or "Certified." Use these flags for production-ready data, and ensure that this dataset is not endorsed, so users know it's not an official or approved dataset.
2) Define and communicate a Dataset Expiry date -> If the dataset is temporary, consider setting an expiration date for it. State that after this date, the dataset can/will be automatically removed or flagged for review.
Pedro Reis - Data Platform MVP / MCT
Making Power BI and Fabric Simple
If my response resolved your issue, please mark it as a solution to help others find it. If you found it helpful, please consider giving it a kudos. Your feedback is highly appreciated!
Find me at LinkedIn
Hi PPStar
If you aim to grant access to both datasets and existing reports but ensure they are not used for production purposes, my suggestion is to flag existing artifacts:
1. Naming Convention: -> Start by naming the workspace clearly to indicate its purpose. For instance, you could name it "Exploratory Workspace - NOT FOR PRODUCTION".
2. Workspace Description: -> Use the workspace description to clearly state its purpose. Mention that the reports and dashboards within are not supported and should not be used for official reporting.
3. Report Watermark: -> Add a watermark to all reports in the exploratory workspace. This can be a text box or an image that says "EXPLORATORY - NOT FOR PRODUCTION" placed in a prominent location on each report page.
4. Notification Banner -> If you have the capability, add a notification banner at the top of each report, reiterating that the report is for exploratory purposes only.
If you aim to grant access just to reports, you might consider granting access exclusively via APP.
If you aim to grant access just to datasets, you might consider disabling build permissions and/or having a separate workspace outside the deployment pipeline as a sandbox for the users.
Pedro Reis - Data Platform MVP / MCT
Making Power BI and Fabric Simple
If my response resolved your issue, please mark it as a solution to help others find it. If you found it helpful, please consider giving it a kudos. Your feedback is highly appreciated!
Find me at LinkedIn
Thank you so much for your response.
Whilst i agree with all of the above, this will work for the actual report.
However, once they have access to the dataset, nothing stops the users from connecting to the dataset using a Live Connection and then build their own reports.
How can we ensure the dataset in EXP is clearly states that data is not production ready.
Hi PPStar
Thanks for the clarification, makes sense. In that case, I suggest the following approaches:1) Use Dataset Endorsement -> In Power BI Service, datasets can be endorsed as "Promoted" or "Certified." Use these flags for production-ready data, and ensure that this dataset is not endorsed, so users know it's not an official or approved dataset.
2) Define and communicate a Dataset Expiry date -> If the dataset is temporary, consider setting an expiration date for it. State that after this date, the dataset can/will be automatically removed or flagged for review.
Pedro Reis - Data Platform MVP / MCT
Making Power BI and Fabric Simple
If my response resolved your issue, please mark it as a solution to help others find it. If you found it helpful, please consider giving it a kudos. Your feedback is highly appreciated!
Find me at LinkedIn