Replies: 4 comments 1 reply
-
|
What am I missing here, is it working for you? |
Beta Was this translation helpful? Give feedback.
-
|
Can this be reopened again @veronicageek |
Beta Was this translation helpful? Give feedback.
-
|
@4iJacob - Please open a new issue in the repo filling the template. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, its old and still not fixed. But its not from Pnp side, its Ms CopyMigration API that is broken. The param is ignored by their API and still is in 2025. I Guess they rather have AI somewhere than fixing their thing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
HI All,
Following this issue which should be fixed I must be doing something wrong: link
Cmdlet "Move-PnPFile -IgnoreVersionHistory" is not working as expected.
Expected behavior
When using "Move-PnPFile -IgnoreVersionHistory" i expect to see in the target site only the last version for the file moved.
Actual behavior
When using "Move-PnPFile -IgnoreVersionHistory" it moves all version history for one file.
Steps to reproduce behavior
$job = Move-PnPFile -SourceUrl $SourceFileURL -TargetUrl $TargetFileURL -IgnoreVersionHistory -AllowSchemaMismatch -NoWait
What is the version of the Cmdlet module you are running?
Using PnP.PowerShell 2.1.1 and PowerShell 7.3.4
Beta Was this translation helpful? Give feedback.
All reactions