Pnpframework: Modern page is not renamed when -TakeSourcePageName is used

Created on 29 Mar 2021  路  4Comments  路  Source: pnp/pnpframework

Problem Area

[ ] Page Transformation: Error during the use of page transformation from PnP PowerShell

Expected or Desired Behavior

Post executing script I was, expecting Classic page is expected to be renamed as "Previous_Pagename.aspx" and the modern to be "Pagename.aspx" after setting the parameter (-TakeSourcePageName) true

Observed Behavior

Classic page is named as "Home.aspx" and modern page as "Migrated_Home" after conversion

Steps to Reproduce

[
I am trying to execute page transformation script for entire site page library.
Step1: Entering the Site URL
Step2 :Entering the value for parameter (-TakeSourcePageName) as Previous or Old

Attaching the script used for reproducing this issue. Thank you so much in advance. Your help would be much appreciated.
]

TransformPageScript_Issue.zip

page transformation 馃 question

All 4 comments

@KiranTalikoti : what version of PnP PowerShell are you using? Can you try the operation with logging enabled and share the created log file

@jansenbe : Sorry for the delayed response. Here is the version of PnP installed in my Win 10 machine.

image

Please find the attached logs. There are 4 pages in the site pages library.
Thank you so much for your kind response on this issue .
Page-Transformation-Report-4-6-2021-10-04-40-AM.zip

@KiranTalikoti Update the PowerShell Module , it should help.

@KiranTalikoti Update the PowerShell Module , it should help.

yes, updated pnp module and it worked.
thank you @divya-akula and @jansenbe for your help.

Was this page helpful?
0 / 5 - 0 ratings