Forum Discussion
Orphaned Content Pack Issue
I am experiencing the same issue, and I was able to reproduce it.
1. Create a workspace called Test Workspace
2. Publish content to it
3. Go to Test Workspace and create a content pack
4. Go to My Workspace and install the content pack via Get Data
5. Go to Test Workspace and delete the group
6. Go to My Workspace.
Result
The content pack published in Test Workspace still exists and is effectively orphaned because the group from which is was published is gone. If there is a way to delete it (un-delete the Test Workspace, for example?), please let me know.
Expected Result
I'll let you guys figure out the experience, but it shoudl be along the lines of either preventing the group from being deleted until all content packs have been manually deleted, or warning that there are content packs published that will be deleted when the group workspace is deleted & ask the user to confirm.
Meanwhile, can I have someone manually delete my orphaned content packs? Tell me what to do... Thanks.
This seems to be resolved. The orphaned content pack is no longer available from Get Data so it looks like Microsoft did a sweep. Thanks!
UPDATE: my orphaned content pack is still there... I must have been testing from a different workspace that did not have permissions.
- Anonymous9 years agoNot applicable
hymieho Nice! Thanks for the update.
- Abenson8 years agoFrequent Visitor
Hi,
I am experiencing the same issue...can't delete a content pack after the group workspace was deleted. Is there a manual approach to removing the content pack. There is no longer a group workspace, so I am thinking that the orpahened content pack will need to be deleted using Power shell or some other utility.
thanks in advance for any assistance provided.