Unable to remove grouped Picture from Presentation - Defect in Presentation Library (ASP.NET Core Office Formats)

Question

Unable to remove grouped Picture from Presentation - Defect in Presentation Library (ASP.NET Core Office Formats)
-------------------------------------------------------------------

To reproduce:

-------------------

1) Build a presentation in PowerPoint such that you have a Picture object (say labeled "SomePicture) and some other control like a TextBox on a slide, then place them in in a grouping. Then add some other object like another TextBox and place the first group and that new object in a group (you effectively have the Picture "SomePicture" in a nested group.

2) Use Syncfusion ASP.NET Core presentation library to open the presentation for manipulation. Attempt to use the Slide.Pictures API or Slide.Shapes API to remove the Picture "SomePicture".

Result

---------------
FAIL - Unable to locate the picture in the Slide.Pictures collection. Also, any attempt to remove it using Slide.Shapes also fails (even though it can be seen as listed).

Is this a known issue: Are there any workarounds for this?

Arun Prasad Matheshwaran · Answer

Hi Michael, 

Thank you for your interest in Syncfusion product. 
We checked the reported scenario - Unable to remove grouped Picture from PowerPoint presentation at our end. We can retrieve the shape collection of a group shape using the below statement, 
IShapes shapes = slide.GroupShapes[0].Shapes; 
Please find the sample created to show how to remove a picture from the group shape of a PowerPoint slide, 
Sample Link: 
http://www.syncfusion.com/downloads/support/forum/127725/ze/HelloWorld-1139270201 

Please review the sample and let us know if it could satisfy your requirement. 

Thanks, 
Arun

Michael Smith · Answer

Thank you very much for your quick and accurate response.  The code example you provided uses the API to successfully resolve my issue/scenario.  I recommend this scenario and API usage be added to your documentation.

Arun Prasad Matheshwaran · Answer

Hi Michael, 

We are glad that your issue has been resolved. We will include this scenario and API details in our documentation. 

Thanks, 
Arun