Avoid Set-PnPClientSideWebPart creating a new version

[p1995]

I'm performing a content migration from classic SharePoint page (SharePoint Online Classic Site. Let's call it source) to Modern site pages(Let's call it destination). In the Source there are many versions so I store the result in the form of array with each item being the information of each version. So In PnP-Powershell i make use of a for loop to push data each iteration. Each iteration, I Update the properties of the Custom content Editor Webpart using Set-PnPClientSideWebPart cmdlet and update the site page columns (like modified date, modified by etc.) using Set-PnPListItem cmdlet. The real issue here is these two cmdlets are creating 2 versions in site Page i.e. if there are 5 versions in source there will be 10 versions in destination. I'm aware I can use -SystemUpdate option in Set-PnPListItem but the Modified by and date columns remains unchanged. So my ultimate requirement is in each iteration I want a new version with updated Webpart properties and modified fields set to the values passed through the PowerShell. Can I pass -SystemUpdate in Set-PnPClientSideWebPart cmdlet or something similar that prevents a new version creation?

These two lines of snippet I have been using inside a for loop below

Set-PnPClientSideWebPart -Page $pagename -Identity 'CustomContentEditor' -PropertiesJson $propertyObjectInJson  (This is creating a new version)

$updateSitePageFields=Set-PnPListItem -List "SitePages"  -Identity $page.PageId -SystemUpdate -Values @{"Modified"=$array[$i].Modified;"Author"=$array[$i].Author.Email;"Created"=$array[$i].Created;"Title"=$array[$i].Title;"DocumentType1"=$array[$i].DocumentType1;"Editor"=$array[$i].Editor.Email} (Currently I have set  -SystemUpdate so a version is not being created on execution)

Please help me with this issue

P.S.: If there a solution to #2916 and #2016, then this will also be the answer to my question

[ToddKlindt]

Are you using the Page Modernization PowerShell to create the new pages? If so, you can do a lot with the mapping files. You might be able to get everything you need done with them removing the need for the Set-PnPListItem step that is creating another version.

[erwinvanhunen]

Sorry, I wrote the message before actually released it and we implemented it differently:

Set-PnPListItem -List [list] -Id [id] -Values @[values] -UpdateType UpdateOverwriteVersion

[erwinvanhunen]

The UpdateType parameter takes 'Update' (the default), 'SystemUpdate' or 'UpdateOverwriteVersion'

[p1995]

UpdateOverwriteVersion is appearing in intellisense but it does nothing. It is as same as not passing any parameters as it created minor versions each time.

[p1995]

Sorry, I wrote the message before actually released it and we implemented it differently:

Set-PnPListItem -List [list] -Id [id] -Values @[values] -UpdateType UpdateOverwriteVersion

Also there is no Parameter called Id. As it is not appearing in intellisense. Do you mean -Identity?

[erwinvanhunen]

Yes. I did it by heart when I wrote the example. There are over 500 cmdlets, it's sometimes hard to remember all the details correct.