…
|
||
---|---|---|
.. | ||
.devcontainer | ||
assets | ||
config | ||
sharepoint/Images | ||
src | ||
teams | ||
.editorconfig | ||
.gitignore | ||
.yo-rc.json | ||
README.md | ||
gulpfile.js | ||
package-lock.json | ||
package.json | ||
tsconfig.json | ||
tslint.json |
README.md
page_type | products | languages | extensions | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
sample |
|
|
|
SPUPS Property Sync
Summary
This component will help the administrators who are currently maintaining the user profiles in their organization. Since not all the properties from Azure are synced automatically to SharePoint UPS, this solution will help administrator to synchronize specific properties (default or custom) from Azure or maintained in a separate system directly to SharePoint UPS using property import. Below are the features
- Property Mapping will provide a flexible and user-friendly way to pick the properties to be synced.
- Templates can be generated based on the 'Property Mapping'.
- Download the generated templates in both CSV & JSON format.
- User selection to allow you to update only the users whose properties are changed or yet to be updated.
- User selection method will allow the admin to update both
- Manually entered properties or which are maintained in a separate system
- Properties from Azure AD
- Bulk Sync will allow the admin to upload the data using the templates generated. They can also use this templates as a base for exporting the data from other system and then feed them here to update the properties.
- Access control based on SharePoint Group, not all the users can access the applictaion.
- Anytime access to the template files generated with different property set and the files uploaded for bulk update.
- Separate section to check the status of the property update. Detailed status on each property and also display the overall status.
- Azure Function to handle the property update. PnPPowershell is used in Azure Function.
- The application supports SPA (Single Page Application).
Note: All the supporting lists were created when the web part is loaded for the first time. Whenever the web part is loaded, the supported lists were checked whether it exists or not.
Properties
-
Select a library to store the templates: A document library to store all the templates generated and also the data files uploaded for bulk sync.
-
Azure Function URL: Azure function URL to run the property update silently.
-
Use Certificate for Azure Function authentication: The video mentioned below to setup Azure Function has different options. This setting will decide whether to use the certificate or stored credentials to communicate with SharePoint.
-
Date format: Date format to be used across the entire application. Used momentJS.
-
SharePoint Groups: Only the users from the configured SharePoint Groups and Site Administrator shall be allowed access.
-
Use page full width: This is used when the web part is added to a site page where it has to use full width.
Note: Only the Site Administrator is allowed to update the application properties.
Preview
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. |
Applies to
Contributors
Version history
Version | Date | Comments |
---|---|---|
1.0.0.0 | Apr 23 2020 | Initial release |
Minimal Path to Awesome
- Clone this repository
- From your command line, change your current directory to the directory containing this sample (
react-spupsproperty-sync
, located undersamples
) - in the command line run:
npm install
gulp bundle --ship && gulp package-solution --ship
- Add the .sppkg file to the app catalog and add the Page Comments web part to the page.
- Azure Function has to be setup for property update. The actual powershell is uploaded in the assets folder. Follow the steps explained in the below video by Paolo Pialorsi.
This sample can also be opened with VS Code Remote Development. Visit https://aka.ms/spfx-devcontainer for further instructions.
Local Mode
This solution doesn't work on local mode.
SharePoint Mode
If you want to try on a real environment, open: O365 Workbench
Video
Help
We do not support samples, but we 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.