sp-dev-fx-webparts/samples/react-feature-framework
Hugo Bernier c24aacbd7f Updated telemetry link 2023-03-12 21:16:15 -04:00
..
.devcontainer added remaining containers 2022-02-16 21:47:07 -05:00
.vscode
assets Changed docs links to learn 2022-10-24 09:42:45 -04:00
config
sharepoint/assets
src/webparts/listProvisioning
typings
.editorconfig
.gitattributes
.gitignore
.npmignore
.yo-rc.json
README.md Updated telemetry link 2023-03-12 21:16:15 -04:00
gulpfile.js
package.json
tsconfig.json
tslint.json

README.md

page_type products languages extensions
sample
office-sp
javascript
typescript
contentType technologies platforms createdDate
samples
SharePoint Framework
react
3/1/2017 12:00:00 AM

Deployment of SharePoint assets as part of SPFx package

Summary

Simplistic solution demonstrating how to provision SharePoint assets using Feature Framework elements when SharePoint Framework solution is being deployed to a SharePoint site.

screenshot

Demonstrated assets getting deployed to SharePoint site are following

  • Fields
  • Content Type
  • List with custom schema

When you install SPFx so site, web scoped feature is activated and associated element.xml files are being processed. Technically you could also provision SharePoint assets using JavaScript, but it is limited to context of the current user using that component. If the user doesn't have sufficient permissions to create or modify SharePoint items, the JavaScript code will not provision those items.

More details on the capability is available from the following article

Compatibility

⚠️ Important
Every SPFx version is only compatible with specific version(s) of Node.js. In order to be able to build this sample, please ensure that the version of Node on your workstation matches one of the versions listed in this section. This sample will not work on a different version of Node.
Refer to https://aka.ms/spfx-matrix for more information on SPFx compatibility.

SPFx 1.0.0 Node.js v6 Compatible with SharePoint Online Compatible SharePoint 2019 Compatible with SharePoint 2016 (Feature Pack 2) Local Workbench Compatible Hosted Workbench Compatible Compatible with Remote Containers

Applies to

Prerequisites

None.

Contributors

Version history

Version Date Comments
1.0 February 27, 2017 Initial sample

Minimal Path to Awesome

  • Clone this repository
  • Move to /samples/react-feature-framework folder
  • in the command line run:
    • npm install
    • gulp bundle
    • gulp package-solution
  • Install react-feature-framework.sppkg from /sharepoint/solution to app catalog in your tenant
  • Install solution to SharePoint site

This sample can also be opened with VS Code Remote Development. Visit https://aka.ms/spfx-devcontainer for further instructions.

Following items are being provisioned

  • SPFxAmount and SPFxCostCenter fields under 'SPFx Columns' group - visible in the Site Column Gallery
  • Cost Center content type using 'SPFx Content Types' group using custom fields - visible in Site Content Types Gallery
  • List called 'SPFx List' using custom schema.xml file using custom content type - visible in site contents page

Help

We do not support samples, but this community is always willing to help, and we want to improve these samples. We use GitHub to track issues, which makes it easy for community members to volunteer their time and help resolve issues.

If you're having issues building the solution, please run spfx doctor from within the solution folder to diagnose incompatibility issues with your environment.

You can try looking at issues related to this sample to see if anybody else is having the same issues.

You can also try looking at discussions related to this sample and see what the community is saying.

If you encounter any issues while using this sample, create a new issue.

For questions regarding this sample, create a new question.

Finally, if you have an idea for improvement, make a suggestion.

Disclaimer

THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.