With the profile completeness extension we can encourage or force users to fill their profiles. This sample SPFx extension renders a profile completeness score. By clicking the score, user can see the score details as shown below:
If you want your SharePoint add-in to appear in SharePoint Store, you need to submit it to the Seller Dashboard for approval. You can add and save your submission as a draft in your Seller Dashboard account until you’re ready to submit it for approval.
This section lists the steps involved in submitting your SharePoint add-in in the Seller Dashboard.
Add a new app
On the overview page, click on Add a new app button
On the listing type page, select SharePoint add-in and click next
On the overview page, provide the mandatory field details as shown below and click next
On the details page, select the necessary languages and provide the mandatory field details as shown below and click next
If you want to prevent the app purchases, select the countries / regions
To get information about users who acquire your add-in, you can submit lead configuration details for your customer relationship management (CRM) system in the Seller Dashboard.
Choose the pricing model fits your need
Save as Draft or Submit
On your summary page, select EDIT DRAFT and make your changes. Select SUBMIT FOR APPROVAL. After your seller account is approved, you can submit your add-in to the Seller Dashboard. You can make changes at any point before you submit for approval, but during the approval process, you won’t be able to make any changes.
Sample SharePoint Framework client-side web part for Microsoft Teams Tab illustrating Video Recording using MediaRecorder Web API.
This is an experimental web part. Because this technology’s specification has not stabilized, check the compatibility table for usage in various browsers. Also note that the syntax and behavior of an experimental technology is subject to change in future versions of browsers as the specification changes
The Sentiment Analysis API provided by Microsoft evaluates text input and returns a sentiment score for each document, ranging from 0 (negative) to 1 (positive). This capability is useful for detecting positive and negative sentiment in social media, customer reviews, and discussion forums. In this article I am going to show you how to send the feedback entered in a SharePoint online modern list item to Sentiment Analysis API and update the response back in SharePoint. Also I am going to show how to beautify the Sentiment score with emojis using column formatting feature.
Create a SharePoint list with the following columns
At the top of the list, click Flow, and then click Create a flow.
Select the below flow template from the right-hand panel.
Follow the instructions on the Microsoft Flow site to connect to the list we have created. Credentials will be verified for each service used in the flow. For Office 365 services such as SharePoint and Outlook, connections will be created automatically. The next steps will be performed in the Microsoft Flow designer. The first action displayed, also known as a trigger, will determine how the flow will be started. Additional actions may be added after the first. Each new action will be dependent on the previous action.
Next step is to add an initialize variable action to set the value of the current Item Id.
Create a POST request using a HTTP action. Set the HTTP Method, URI, Headers and Body as shown below:
Note: Login to Azure and get the Ocp-Apim-Subscription-Key. Refer this article for steps.
Now let us parse the sentiment score from the response we received from the HTTP action and save the value in a variable using initialize variable action as shown below
Microsoft Teams is a chat-based workspace that brings together people, conversations, content, and tools for easier collaboration. SharePoint sites include the modern page feature, which allow you to engage the team members with important or interesting stories. Here I am going to show you how to display a SharePoint modern page with in teams as a tab.
I have created a SharePoint modern page as show below:
Set up SharePoint Modern Page in Teams
In Teams, navigate to the team where you want your SharePoint page to appear.
Click the plus sign to add a new tab.
Click on Website
Provide a Tab name and SharePoint Modern page url and click Save. Optionally we can select Post to the channel about this tab check box to communicate this change with the users.
That’s it! Now, every time you visit your team, the newly added tab will appear as part of the teams as shown below
You can use the expand / collapse button to view the content the way you like
I don’t know if you noticed, but the out of the box sharepoint controls such as Suite Bar, Left Navigation, Search Box, Page Title Area and Command Bar are gone within teams.
If you have custom webparts within the page, you can not edit properties of those within teams.
You can not change the web part arrangement sequence within teams.
After upgrading the SQL Server Reporting Service to 2016, the SSRS reports embedded in different applications including SharePoint pages using an iframe tag or page viewer web parts were stopped rendering.
I tried to fix this issue by adding the following entries in the rsreportserver.config but no luck.
The rsreportserver.config file is installed in the following location by default:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\WebServices\Reporting
In SharePoint there used to be a ‘copy shortcut’ option in the right-click menu on a document. This feature is not available currently. Now we need to go to the share sub-menu to get a link to the document, but what is offered there is the docidredir link, not the full path.
This SPFx extension opens a dialog where the user can see the document full path. The Email Link button helps the user to share the link via default email client.
The first step is to create a SPFx Git Repository Project in VSTS.
Let us clone the newly created Git project into your favorite local folder using the following git command
git clone -b master repopath
SharePoint Framework(SPFx) Web Part Setup
Go to the project directory using command prompt/ terminal and set up your SPFx Web Part project as explained here. I am going to use my sample code here but feel free to write your own logic in your SPFx Web Part.
This is my project folder structure
One Time Activity
Let us package artifacts and upload the files in app catalog site and CDN library.
Open the write-manifests.json file under config folder and update the cdnBasePath parameter with your CDN SharePoint Document Library path.
Make sure you are still in the project directory you used to set up your web part project. In the console window, execute the following gulp task:
This will build the minified assets required to upload to the CDN library in temp\deploy directory. Go to your CDN SharePoint Library and upload the generated files.
In the console window, execute the following gulp task to package your client-side solution that contains the web part:
The command will create the .sppkg package file in the sharepoint/solution.
Go to your App Catalog site and upload the generated .sppkg file to the App Catalog. This will deploy the client-side solution package. SharePoint will display a dialog and ask you to trust the client-side solution to deploy. Click deploy.
At this point the web part is ready to be used on a page. Open a site where you want to test the web part and go the Site contents page of the site. Choose Add – App from the toolbar and choose the your app to be installed on the site.
After the app has been installed, add the webpart in a page
Check-in the code and push the same to master branch via Visual Studio Code editor.
At this point we are ready integrate our SPFx web part project repository with VSTS continuous build and release process.
Upload the highlighted custom gulp tasks provided by Elio Struyf and install the necessary npm packages as per the instruction given.
Update the gulpfile.js as shown below:
Continuous Integration and Delivery Setup in VSTS
Switch back to VSTS
Go to build & release section and click New button
Select the empty template and click Apply.
Configure the following variables for the build and release. Adjust the values as per your environment.
Add the following tasks and configure it as shown below
NPM Install – npm
Update CDN Location – Gulp
Bundle Project – Gulp
Package Solution – Gulp
Upload Files in CDN – Gulp
Upload App Package to App Catalog – Gulp
Deploy App – Gulp
Also enable the continuous integration settings so that the build process starts when the latest code is checked-in in master branch.
All done. Now it is time to test our continuous build and release process by pushing a new code change to git repository and check build process get triggered.
Let us change the progress bar color to red and check-in the latest change to git.
Commit & Push Code Changes
Build and Release Status
As you can see in the screenshot, the latest code got updated and progress bar color is reflecting.
Note: You can isolate the deployment process from the build process using a release template.