New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is it possible to create a page based on a custom template using the Graph API? #9653
Comments
Hi @roberAlb! It seems that currently, there's no straightforward method available in the pages API. However, you can achieve the same effect by following this procedure:
Let me know if that works for you. |
Hi @mkm17 thanks for your message, but I don't think it's going to work, bacause the page template contains some custom webparts and they are not allowed as far as I'm reading. |
Hi @roberAlb I quickly tested the same method with my custom SPFx web part, and it successfully created a new page with non-standard Microsoft web parts. |
Hi @mkm17 again, I was making some tests and looks like is working, it was giving me just an error about an OOTB Yammer web that is not supported, but after removing it, the request worked, Thanks!! However there is an important point for us as well here, which is the content type, the template has a content type assigned but it's not coming when trying to get it as I cannot see any property to specify it. Thanks again, |
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
馃挜 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested
Additional environment details
No response
Issue description
Basically we were exploring Graph API to create SP pages but our scenario are based on custom template created by us, so we wanted to clarify is there is a way to create a page based on a custom template. We didn't see anything as part of the documentation and we would like to know if this is in the roadmap or not. Thanks.
The text was updated successfully, but these errors were encountered: