Pnp-powershell: Notebook Link broken

Created on 3 Jan 2020  Â·  5Comments  Â·  Source: pnp/PnP-PowerShell

Notice: many issues / bugs reported are actually related to the PnP Core Library which is used behind the scenes. Consider carefully where to report an issue:

  1. Get-SPOProvisioningTemplate
  2. The code...

Reporting an Issue or Missing Feature

Notebook links are not being created correctly.

https://github.com/MicrosoftDocs/office-docs-powershell/issues/4584?email_source=notifications&email_token=AEGDMM7ALVYTMG3CJS2P323Q3HIOPA5CNFSM4J7NUTKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH2B6NI#issuecomment-569646901

Expected behavior

Should link the notebook correctly.

Actual behavior

The link created is broken, and getting a 404 error upon clicking the quick link.

Steps to reproduce behavior

Create a template with the notebook quick link included, apply template. Try and click on the notebook.

Which version of the PnP-PowerShell Cmdlets are you using?

  • [ ] PnP PowerShell for SharePoint Online

What is the version of the Cmdlet module you are running?

PS C:\WINDOWS\system32> Get-Module -Name pnppowershell -ListAvailable

Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Binary 3.14.19... SharePointPnPPowerShellOnline {Add-PnPAlert, Add-PnPApp, Add-PnPClientSidePage, Add-PnPClientSidePageSection...}

How did you install the PnP-PowerShell Cmdlets?

  • [ ] MSI Installed downloaded from GitHub
Needs

Most helpful comment

Hi, I have seen the same issue with apply-pnpprovisioningtemplate when overwriting the existing leftnav.
When the target site is create the navigation node for the Onenote looks like /blank14/_layouts/15/WopiFrame.aspx?sourcedoc=%7B20f5723f-9319-4615-bedf-e9502416780f%7D&action=editnew

However once the navigation has been updated from the template file the navigation node now looks like this ( WopiFrame.aspx has been replaced by Doc.aspx and the GUID has been changed):

/sites/blank14/_layouts/15/Doc.aspx?sourcedoc=%7Bfaddfd22-c346-49e8-8a3f-55941c122086%7D&action=editnew

The only workaround I have found is to update the Navigation Node in the XML to link to {site}/SiteAssets/Team%20Site%20Notebook . It works but it is a hack

All 5 comments

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

Hi, I have seen the same issue with apply-pnpprovisioningtemplate when overwriting the existing leftnav.
When the target site is create the navigation node for the Onenote looks like /blank14/_layouts/15/WopiFrame.aspx?sourcedoc=%7B20f5723f-9319-4615-bedf-e9502416780f%7D&action=editnew

However once the navigation has been updated from the template file the navigation node now looks like this ( WopiFrame.aspx has been replaced by Doc.aspx and the GUID has been changed):

/sites/blank14/_layouts/15/Doc.aspx?sourcedoc=%7Bfaddfd22-c346-49e8-8a3f-55941c122086%7D&action=editnew

The only workaround I have found is to update the Navigation Node in the XML to link to {site}/SiteAssets/Team%20Site%20Notebook . It works but it is a hack

Here is a possible solution: https://github.com/pnp/PnP-Sites-Core/issues/1915

{site}/_layouts/15/groupstatus.aspx?Target=NOTEBOOK

Worked for me 😊

{site}/SiteAssets/_Team%20Site_%20Notebook

But aren't the notebooks on the site template and newly created site named after their site?

No. You have to create the notebook first. THEN update link/apply provisioning template (on a side note, same with Planner as well).

HTHs

Sent from my iPad

On Aug 21, 2020, at 5:56 AM, PittsburghSharePointPro notifications@github.com wrote:


{site}/SiteAssets/Team%20Site%20Notebook

But aren't the notebooks on the site template and newly created site named after their site?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Was this page helpful?
0 / 5 - 0 ratings