top of page

Retrieve Webparts From Page Using CSOM With PowerShell On SharePoint


In this article, you will learn how to get web parts and its properties from a publishing page using CSOM with PowerShell for any SharePoint platform site.

Steps Involved

The following section explains the flow for getting web parts from a publishing page.

a. Add the references using the Add-Type command with necessary reference paths. The necessary references are Microsoft.SharePoint.Client.dll, Microsoft.SharePoint.Client.Runtime.dll and Microsoft.SharePoint.Client.Publishing.dll.

  1. Add-Type -Path "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.dll"

  2. Add-Type -Path "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Runtime.dll"

  3. Add-Type -Path "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI\Microsoft.SharePoint.Client.Publishing.dll"

b. Initialize client context object with the site URL.

  1. $siteURL = ""

  2. $ctx = New-Object Microsoft.SharePoint.Client.ClientContext($siteURL)  

c. If you are trying to access SharePoint Online site, then you need to setup the site credentials with credentials parameter and get it set to the client context. 

  1. # Not required for on premise site - Start

  2. $userId = ""

  3. $pwd = Read-Host -Prompt "Enter password" -AsSecureString  

  4. $creds = New-Object Microsoft.SharePoint.Client.SharePointOnlineCredentials($userId, $pwd)  

  5. $ctx.credentials = $creds   

  6. # Not required for on premise site - End

d. If you are trying to access the SharePoint on premise site, then the credentials parameter is not required to be set to the context. But you need to run the code on the respective SharePoint server.

e. Get the page from the respective library using server relative url. Load the file and execute the query to access the page components.

  1. # page to be viewed $pageName = "TestPage1.aspx"

  2. # Get the page

  3. $file = $ctx.Web.GetFileByServerRelativeUrl("/Pages/TestPage1.aspx")  

  4. $ctx.Load($file)  

  5. $ctx.ExecuteQuery()  

f. Then from the page, we will get the web parts present. From the file object, using web part manager and personalization scope we can access the page web parts. Load and execute the query to access the web parts.

  1. # Get all the webparts Write-Host "Retrieving webparts"

  2. $wpManager = $file.GetLimitedWebPartManager([Microsoft.SharePoint.Client.WebParts.PersonalizationScope]::Shared)  

  3. $webparts = $wpManager.Webparts  

  4. $ctx.Load($webparts)  

  5. $ctx.ExecuteQuery()  

g. Access the web parts.

  • Check the web part count and if web parts present, access the individual web parts using foreach loop.

  • For each web part, the context should be loaded with web part properties and executed.

  • Then $webpart. Id will get us web part GUID and $webpart.WebPart.Properties.FieldValues will have all the properties defined for a web part. you can use foreach loop to get the necessary properties.

  1. if($webparts.Count -gt 0){      

  2. Write-Host "Looping through all webparts"     

  3. foreach($webpart in $webparts){          

  4. $ctx.Load($webpart.WebPart.Properties)          

  5. $ctx.ExecuteQuery()          

  6. $propValues = $webpart.WebPart.Properties.FieldValues          

  7. Write-Host "ID: $"         

  8. foreach($property in $propValues){              

  9. Write-Host "Title: " $property.Title                              

  10. Write-Host "Description: " $property.Description              

  11. Write-Host "Chrome Type: " $property.ChromeType          

  12. }       }  

  13. }  

Like wise other properties can also be retrieved. The following snapshot shows the properties which can be retrieved for any web part present on the page. This image shows the content editor web part properties present on the page.


Thus you have learned how to access the web parts and its properties from a publishing page on any SharePoint platform site using CSOM with PowerShell commands.



bottom of page