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.
Steps to reproduce an erroneous behavior of Workspace :
1. Log in to Power BI
2. Create a Workspace
3. Create a Content Pack from the Workspace, and share it with "Entire Organization"
4. Delete the Workspace just created
5. Now you have a stranded Content Pack which can be accessed by everyone in the organization but cannot be managed / edited / removed any more.
Please help resolve this issue.
Cheers,
Gin
Hi @jxjia,
Once you delete the group that contains a content pack, the content pack will still be visible in library and is effectively orphaned. I can reproduce your issue.
Currently, we can’t delete this content pack. We have to make sure that the Content Packs are deleted prior to deleting the Power BI Group.
Thanks,
Lydia Zhang
Hi @v-yuezhe-msft,
Thanks for your reply .
Are you able to suggest any alternatives for removing such Content Packs ? including an action by Microsoft.
Cheers,
Gin
Hi @jxjia,
Based on my test, there is no method that can be used to delete the content pack. And this issue has been reported internally, I will post back once I get any update.
Thanks,
Lydia Zhang
I created a request to add this functionality - check it out and VOTE:
I soooooo want to test reproducing this issue, but I also don't want a stranded content pack out there. Conflicted!! What happens if you recreate the Workspace with the same name?
Hi smoupre,
Completely understand your impulse to check the behavior in eyes. I was shocked when I heard it the first time too.
I tried re-creating the Workspace with identical name and case, but it didn't help. Apparently it was managed by GUID instead of neme.
Thanks for offering your wisdom !!
Cheers,
Gin
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 |
---|---|
58 | |
20 | |
19 | |
18 | |
9 |