[X] Bug
[ ] Enhancement
[ ] 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...
Mapping not working - PS PowerShell no errors raised
Raising because cant fix until late tonight.
ConvertTo-PnPClientSidePage -Identity "Secret-Sauce-Recipe.aspx" -PublishingPage -TargetConnection $spOnlineConn -Connection $sp13Conn -Overwrite -ClearCache -LogType Console -PageLayoutMapping c:\temp\onprem-mapping-all-test.xml -UserMappingFile C:\temp\usermapping.csv -LogVerbose
CSV Snippet
ALPHADELTA\SPInstall,[email protected]
S-1-5-21-2364077317-3999105188-691961326-1103,[email protected]
c:0+.w|s-1-5-21-2364077317-3999105188-691961326-1129,c:0t.c|tenant|c293ebb4-5999-414f-b0c5-16e7a618db21
s-1-5-21-2364077317-3999105188-691961326-1128,Transform-Group
alphadelta\testuser1,[email protected]
Some notes for repo:
@pkbullock : Permission management will not work with contribute permissions...can you retry with being administrator on both target site as source site?
Sorry, might not have been clear in the reproduction info, the transform accounts are admin.
I鈥檒l be able to check around 5pm later on. On client site at the moment.
I'll try this from SP2013 with PS and update here
Found something not working with querying the user list...let me dive into it
@pkbullock : I did fix several things: https://github.com/SharePoint/sp-dev-modernization/commit/b93267385c4f295b62cb51538ac7d7051e59009a. Please test again and let me know. If needed I can still do some changes this evening, tomorrow morning...but the release will have to go out tomorrow
I have managed to get this working with the latest dev code. I found the root cause, is that i had blocked some of the test users in my tenant - which meant that they do not resolve in SPO and not getting the expected results. Thanks for looking into this!
This might be an enhancement opportunity to show this had occurred in reporting.
OK, closing this issue then. Thanks for the extra testing :-)