ConvertTo-PnPPage error The collection type 'System.Collections.Generic.Dictionary`2[System.UInt32,System.String]' is not supported
See original GitHub issueHi!
I’m trying to run the command ‘ConvertTo-PnPPage’ but this returns the error: ‘ConvertTo-PnPPage : The collection type ‘System.Collections.Generic.Dictionary`2[System.UInt32,System.String]’ is not supported.’
This command works fine with the ‘SharePointPnPPowerShellOnline’ module.
There is no logfile created with the Set-PnpTraceLog and because of the error message I thought this was something with libraries being loaded incorrectly. Is this correct and therefore the right place to submit this error?
Full cmdlet:
ConvertTo-PnPPage -PublishingPage -Identity "<url>" -Overwrite -TargetWebUrl $targetUrl
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
[BUG] ConvertTo-PnPPage: The collection type 'System. ...
BUG : ConvertTo-PnPPage not working when trying to convert a publishing page. Error message: ConvertTo-PnPPage : The collection type 'System.
Read more >c# - Cannot convert type 'System.Collections.Generic. ...
It's because when you loop through items in a Dictionary, the item within the Dictionary is not a Dictionary, it's a KeyValuePair.
Read more >The collection type Dictionary with integer Key not supported
Issue resolution for error serilzation error The collection type 'System.Collections.Generic.Dictionary`2[System.Int32,System.String]' is not supported.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Allright, I made a stupid mistake and connected to the wrong site, so the bug is actually fixed (no more error messages)! Thanks for the bug fixing and sorry for the confusion 😃
@jansenbe absolutely, it will be monday morning and I will post te result here