modernization: The Modernized page created doesn't have the original Created By, Modified By, or Contact user information.
Category
[X] Bug [ ] Enhancement
Problem Area
[ ] Page Transformation: Error during the setup/use of the Page Transformation UI solution (did you check our troubleshooting guide?) [X] Page Transformation: Error during the use of page transformation from PnP PowerShell [ ] Page Transformation: Error during the use of page transformation from .Net [ ] Page Transformation: Page is not looking correct after transformation [ ] Modernization Scanner: something went wrong…
Expected or Desired Behavior
Expect the Original Created By, Modified By, and Contact to be retained during the transformation.
Observed Behavior
The Created By, Modified By, and Contact are not being Retained during the transformation. All fields are being replaced with the user performing the Transformation.
Steps to Reproduce
# 1 connection the target site
$target = Connect-PnPOnline https://tenant.sharepoint.com/sites/modernsite/ -ReturnConnection
# 2 Connect to your on-premises portal
Connect-PnPOnline https://ClassicSite.ourdomain.com -CurrentCredentials
# 3 Using Powershell Convert the Classic Page to Modern using ConvertTo-PnPClientSidePage
ConvertTo-PnPClientSidePage -Identity $Name -PublishingPage -overwrite -TargetConnection $target -PageLayoutMapping c:\temp\pagemap.xml -CopyPageMetadata -LogVerbose -LogType File -LogFolder c:\temp\Log
**# 4 View generated Log - Page-Transformation-Report**
> # Modernisation Summary Report
>
> Date | Duration | Source Page | Target Page Url | Status
> ------------- | ------------- | ------------- | ------------- | -------------
> 9/3/2019 9:04:03 AM | 00:00:06 | [/pages/partner.aspx](https://ClassicSite.ourdomain.com/pages/partner.aspx) | [/sitepages/pages/partner.aspx](https://tenant.sharepoint.com/sites/tdpartners/sitepages/pages/partner.aspx) | Successful with 6 warnings and 0 non-critical errors
> ## Warnings during transformation
>
> Date | Source Page | Operation | Message
> ------------- | ------------- | ------------- | -------------
> 9/3/2019 9:04:03 AM | /pages/partner.aspx | Input Validation | Keep Specific Permissions was set, however this is not currently supported when contexts are cross-farm/tenant - this feature has been disabled
> 9/3/2019 9:04:08 AM | /pages/partner.aspx | Article page handling | Page could not be published as versioning is not enabled or version stamp could not be set.
> 9/3/2019 9:04:08 AM | /pages/partner.aspx | Copying page metadata | Skipped copying field: Author
> 9/3/2019 9:04:08 AM | /pages/partner.aspx | Copying page metadata | Skipped copying field: Editor
> 9/3/2019 9:04:09 AM | /pages/partner.aspx | Copying page metadata | Skipped copying field: Author
> 9/3/2019 9:04:09 AM | /pages/partner.aspx | Copying page metadata | Skipped copying field: Editor
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (9 by maintainers)
Hi @gautamdsheth ,
I’ve introduced a new generic option to handle Author/Editor/Created/Modified via the KeepPageCreationModificationInformation flag in both .Net as PowerShell. This will be part of the October release. Given that we’ve no account mapping yet, this feature does not work when the source page is not in SPO, once we’ve account mapping this can be updated.
For now I’ll close this issue, feel free open a new one if you still have issues when testing with the new options.
Note: please drop setting the Author/Editor/Created/Modified fields from your page layout mappings if you’re using the new feature.