The request message is too big. The server does not allow messages larger than 2097152 bytes.

[gopaldahal]

Category

• Bug

Describe the bug

Creating site pages with content larger than 2Mb throws unhandled exception.

Steps to reproduce

var libraryTitle = "SitePages"; var parentList = context.Web.Lists.GetByTitleAsync(libraryTitle, l => l.Title, l => l.Fields).Result; var content = System.IO.File.ReadAllText("D:\\Desktop\\pagewithtextstringlargerthen2mb.txt"); var page = context.Web.NewPage(); page.AddSection(CanvasSectionTemplate.OneColumn, 1); page.AddControl(page.NewTextPart(content), page.Sections[0].Columns[0]); page.Save("Heyram1.aspx");

Expected behavior

There should have been no exception

Environment details (development & target environment)

• SDK version: [1.6.0 ]
• OS: [Windows 10 ]
• SDK used in: [Console App]
• Framework: [.NET Framework v4.7.2 ]
• Tooling: [Visual Studio 2022]

Additional context

Thanks for your contribution! Sharing is caring.

[jansenbe]

Hey @gopaldahal , unfortunately this is a SharePoint Online limitation that cannot be configured (you should do this in on-premises SharePoint). When updating a page we actually update some fields in the page list item and when the total size of the list item update request exceeds the threshold this error is thrown. At the moment there's unfortunately nothing I can do about this and therefore I'll have to close this issue. The real solution will have to come with an official modern pages API, but that's not available at this moment. Hope you're not having too many of these big text parts? Alternatively split the page in multiple pages?

[heinrich-ulbricht]

Ran into this as well. I think I spotted an if somewhere checking if Graph should be used. Is there a modern API yet for large pages > 2 MB? @jansenbe

[jansenbe]

@heinrich-ulbricht : we're close to providing a beta version of the Graph pages API, integrating this API in PnP Core SDK however will take a while as we need a v1.0 version first and need to ensure we've full compatibility. Don't know your scenario, but using the beta Graph API might be a solution once it's available.

[heinrich-ulbricht]

@jansenbe Good to know, thanks for the feedback. Beta Graph API would be an option if it worked without issues. Breaking API changes (renamings etc.) might be something we can live with, flaky provisioning results or restrictions in functionality not so much (the page content is controlled by the user). This issue currently affects about 0.01% of pages which puts it a bit into perspective, though.

[heinrich-ulbricht]

Excited for the Graph pages API to be available in March 2024 :D