6 thoughts on “SharePoint Online and Copied Metadata

  1. Thanks Ian! You saved us a lot of headaches with this fix. All the Microsoft forums and uservoice suggested changing the ParserDisabled property was not possible on SharePoint Online, so it was a relief to come across your article with a solution.

  2. This is the most underrated webpage in all of SharePoint. Our company wouldn’t have migrated our data to SharePoint if I hadn’t found this information here. Thank you so much, and good work!

    Microsoft really needs to create a function for users to easily turn this on or off. The fact that SharePoint modifies files on its own essentially rules it out for anyone who cares about data integrity.

  3. Thank you sooooo much for this! We have an approval workflow running on procedures. The approved ones are converted to pdf, until then they are .docx types. Applying new templates caused loss of important metadata concerning the approval process and history. Coming from on premise first did not know what hit us…

  4. Wow thank you so much for this. This has really been doing my head in about SharePoint how it tampers with the binary contents of the file of a doc/docx/xlsx etc. https://docs.microsoft.com/en-us/sharepoint/technical-reference/default-crawled-file-name-extensions-and-parsed-file-types

    It makes things tricky when you need to run a tool to verify that the file has copied across correctly without corruption or you need to re-migrate a portion of it and need to figure out what has changed or not.

    In the end I couldn’t find the DLLs from the download, but eventually I did find them in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\ISAPI but then I couldn’t get past the MFA login and couldn’t be bothered to set up an App password, so I found a different way of doing it using the CLI for Microsoft 365.

    I documented the process I took here:


  5. I tried below code for MFA enabled site and it worked. P.S. u need to uninstall PnP powershell module “Uninstall-Module -Name pnp.powershell” and install SharePoint PnP PowerShell module before “Install-Module -Name SharePointPnPPowerShellOnline -Force”. As I searched SharePoint Online PowerShell Modules don’t work well with Dlls, so you might need to uninstall them as well.
    Here’s the script:

    Add-Type -Path “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.dll”
    Add-Type -Path “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.Client.Runtime.dll”
    Add-Type -Path “C:\Program Files\WindowsPowerShell\Modules\SharePointPnPPowerShellOnline\3.29.2101.0\OfficeDevPnP.Core.dll”
    $SiteURL= ” ”
    $ListName=” ”
    try {
    $Ctx = New-Object Microsoft.SharePoint.Client.ClientContext($SiteURL)
    $AuthenticationManager = new-object OfficeDevPnP.Core.AuthenticationManager
    $ctx = $AuthenticationManager.GetWebLoginClientContext($siteURL)
    $List=$Ctx.Web.Lists.GetByTitle(” “)
    Write-host “Parser Disabled value prev ” $List.ParserDisabled
    $List.ParserDisabled = $true
    Write-host “Parser Disabled value new ” $List.ParserDisabled
    Catch {
    write-host -f Red “Error:” $_.Exception.Message
    Fill the site and library details and check if it works!

Leave a Reply

Your email address will not be published. Required fields are marked *