Creating site templates that include preconfigured web parts on the landing page is a common requirement. We can add and configure classic OOB web parts on a landing page and save the site as a template, and we can do script injection customisations and save the site as a template. However, if a site includes an SPFx web part, we get the error message:
"Sorry, this site can't be saved as a template. It contains apps that don't work in templates"
This is currently a blocker in an area where a SharePoint Framework approach would otherwise be ideal.21 votes
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
We do recommend having a look at the remote provisioning patterns (Site Designs or PnP Provisioning) which are future proof as the existing old save-site-as-a-template is not really something we recommend to be used as such.
Update framework1 vote
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not detailed enough for us to perform any action actions.
The urls do not redirect, any ideas why? I have this issue:1 vote
Closing as this is not an enhancement. It’s a potential issue in existing capability and reporting these in UserVoice is not the right way to get things sorted out.
Right now SharePoint Framework Extensions support three different types of extensions: ApplicationCustomizers, FieldCustomizers and CommandSets . Can we combine two extensions under one project. Example: Based on selected List items in the list, do some customization in the header bar using Application Customizer. Please suggest.1 vote
This is absolutely supported and you can have as many extensions or web parts in single solution talking between each other. There are numerous options for the components to communicate with each other. One of such options is demonstrated in following sample in SharePoint GitHub – https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-rxjs-event-emitter. Since this is not really a new feature request, we will close the issue. Would suggest having questions and discussions in StackExchange, GitHub or in SP Tech Community.
Get-PnPTenantSite -Detailed -IncludeOneDriveSites
We would like to have the following:
• we would like to be able to target only onedrive sites and/or group sites
• we would like the report to run quickly as per the GUI report in the admin console - that seems to run a similar query in about 2 min.
• we would like a report to show all onedrives / groups / sites created after date1 vote
Thank you for your input around the SharePoint PnP PowerShell. PnP CommandSets are however not part of the official product, so we support and have a discussion around them in the GitHub. In this case, would suggest creating a new entry to the issue list in the PnP-PowerShell repository at https://github.com/SharePoint/pnp-powershell/issues with these details. Asks are understandable and absolutely reasonable. Do also remember that PnP effort is dependent on the community contributions, so we cannot guarantee on the timelines for addressing any requests.
Thx for your suggestion and time taken for providing us your input.
When I create a new SPFx webpart, "$schema" path is wrong in WebPart.manifest.json. It must be "client-side-component-manifest.schema.json", but current is "clientSideComponentManifestSchema.json".1 vote
Thx for submitting this. This is clearly a bug and should have been already addressed with the v1.2 release. In future, if you have seen any specific bugs or random issues, we would recommend using https://github.com/SharePoint/sp-dev-docs/issues issue list to start a discussion with SharePoint engineering. Uservoice is mainly for the new feature requests and possible issues can, unfortunately, get hidden here. Thx anyway for the submission and please let us know in the issue list if you still have any questions.
- Don't see your idea?